linux-kernel - Re: oom kill oddness.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20060929213411.GG22014@redhat.com>
Date:	Fri, 29 Sep 2006 17:34:11 -0400
From:	Dave Jones <davej@...hat.com>
To:	Larry Woodman <lwoodman@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: oom kill oddness.

On Fri, Sep 29, 2006 at 04:03:14PM -0400, Larry Woodman wrote:

 > Dave, this has been a problem since the out_of_memory() function was 
 > changed
 > between 2.6.10 and 2.6.11.  Before this change out_of_memory() required 
 > multiple
 > calls within 5 seconds before actually OOM killed a process.  After the 
 > change(in 2.6.11)
 > a single call to out_of_memory() results in OOM killing a process.  The 
 > following patch
 > allows the 2.6.18 system to run under much more memory pressure before 
 > it OOM kills.

Some of these tests do seem to be readded in Linus' current tree.

[PATCH] oom: don't kill current when another OOM in progress

went in earlier today for eg.
I'm curious why these checks were ever removed in the first place though.

	Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/