| 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: <20070723141641.5759a287.akpm@linux-foundation.org> Date: Mon, 23 Jul 2007 14:16:41 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: will_schmidt@...t.ibm.com Cc: Geert Uytterhoeven <geert@...ux-m68k.org>, Christoph Hellwig <hch@...radead.org>, Andi Kleen <ak@...e.de>, linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org Subject: Re: [PATCH respin, was PATCH for review] During VM oom condition, kill all threads in process group On Mon, 23 Jul 2007 13:09:45 -0500 Will Schmidt <will_schmidt@...t.ibm.com> wrote: > During VM oom condition, kill all threads in process group. > > We have had complaints where a threaded application is left in a bad > state after one of it's threads is killed when we hit a VM: out_of_memory > condition. > Killing just one of the process threads can leave the application in a > bad state, whereas killing the entire process group would allow for > the application to restart, or be otherwise handled, and makes it very > obvious that something has gone wrong. > > This change allows the entire process group to be taken down, rather > than just the one thread. Just checking... blackfin h8300 m68knommu uml v850 were not changed. Intentional? - 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