Messages in this thread |  | | Date | Thu, 14 Apr 2011 09:57:42 +0900 | Subject | Re: [PATCH 0/4] forkbomb killer | From | Minchan Kim <> |
| |
Hi, KOSAKI and Kame.
On Thu, Apr 14, 2011 at 9:35 AM, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote: > On Thu, 14 Apr 2011 09:20:41 +0900 (JST) > KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote: > >> Hi, Minchan, Kamezawa-san, >> >> > >> So whenever user push sysrq, older tasks would be killed and at last, >> > >> root forkbomb task would be killed. >> > >> >> > > >> > > Maybe good for a single user system and it can send Sysrq. >> > > But I myself not very excited with this new feature becasuse I need to >> > > run to push Sysrq .... >> > > >> > > Please do as you like, I think the idea itself is interesting. >> > > But I love some automatic ones. I do other jobs. >> > >> > Okay. Thanks for the comment, Kame. >> > >> > I hope Andrew or someone gives feedback forkbomb problem itself before >> > diving into this. >> >> May I ask current status of this thread? I'm unhappy if our kernel keep >> to have forkbomb weakness. ;) > > I've stopped updating but can restart at any time. (And I found a bug ;) > >> Can we consider to take either or both idea? >> > I think yes, both idea can be used. > One idea is > - kill all recent threads by Sysrq. The user can use Sysrq multiple times > until forkbomb stops. > Another(mine) is > - kill all problematic in automatic. This adds some tracking costs but > can be configurable. > > Thanks, > -Kame > >
Unfortunately, we didn't have a slot to discuss the oom and forkbomb. So, personally, I talked it with some guys(who we know very well :) ) for a moment during lunch time at LSF/MM. It seems he doesn't feel strongly we really need it and still I am not sure it, either.
Now most important thing is to listen other's opinions about we really need it and we need it in kernel.
And I have a idea to implement my one in automatic, too. :)
Thanks for your interest.
-- Kind regards, Minchan Kim -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |