[lkml]   [2000]   [Mar]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: oom killing
> On Tue, 29 Feb 2000, Roman Zippel wrote:
> >Oh, that's even gets better. If you push that a little harder, it even
> >kills init and then it's time to press the reset button (even alt-sysbrk
> >won't save you from a fsck :( ).
> This patch fixes the oom troubles:
> ftp://ftp.*

Can you give brief description what whatw as wrong/how if it is fixing.

upbon brief look it seems to me that a) init get preferential treatment,
b) it tries to kill them more gracefully.

And for that matter, wouldn't it be better to simply disable memory
overcommiting by default? I think it is unreasonable to expect to have
random process killed on _momentary_ out of memory thing. This opens way
to simple, and *very* effective Denial-Of-Service attack. You no longer
run box out of memory, you further cause other processes get killed.

A program expect ENOMEM error, and not giving it is kind of cheating on
it and defiant from what the program expect. Thus IMHO I think the
'memory overcommit' shoud be off by default.

Am I wrong here?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:56    [W:0.055 / U:2.000 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site