| 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
| ||
|
Message-ID: <20090113213316.GB27227@ioremap.net> Date: Wed, 14 Jan 2009 00:33:16 +0300 From: Evgeniy Polyakov <zbr@...emap.net> To: David Rientjes <rientjes@...gle.com> Cc: Balbir Singh <balbir@...ux.vnet.ibm.com>, Alan Cox <alan@...rguk.ukuu.org.uk>, Dave Jones <davej@...hat.com>, linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [why oom_adj does not work] Re: Linux killed Kenny, bastard! On Tue, Jan 13, 2009 at 11:46:14AM -0800, David Rientjes (rientjes@...gle.com) wrote: > Children are already preferred over the chosen parent task, as I've > explained a few times. When a task is identified for oom kill by the > badness heuristics, the oom killer attempts to kill a child that does not > share the same mm first, which is exactly what you're asking for here. If > the parent shares the mm, it needs to exit as well before memory freeing > may occur. I really did not investigate why it happend, but oom'ed machine had killed cgi daemons and parent process itself. And ssh to the heap. While it should be enough just to kill appropriate daemon. Apparently things are not that shine as should be. -- Evgeniy Polyakov -- 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/
Powered by blists - more mailing lists