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
| ||
|
Date: Tue, 17 Apr 2007 20:24:35 -0400 From: Larry Woodman <lwoodman@...hat.com> To: Christoph Lameter <clameter@....com> Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] sysctl_panic_on_oom broken On Tue, 2007-04-17 at 14:39 -0700, Christoph Lameter wrote: > > It recreates the old problem that we OOM while we still have memory > in other parts of the system. How, by the time we get here we have already decided we are going to OOMkill or panic. This change just obeys sysctl_panic_on_oom before killing current. ----------------------------------------------------------------------- /* check if we are going to panic before enything else... */ if (sysctl_panic_on_oom) panic("out of memory. panic_on_oom is selected\n"); /* * Check if there were limitations on the allocation * NUMA) that may require different handling. */ switch (constrained_alloc(zonelist, gfp_mask)) { case CONSTRAINT_MEMORY_POLICY: oom_kill_process(current, points, "No available memory (MPOL_BIND)"); break; case CONSTRAINT_CPUSET: oom_kill_process(current, points, "No available memory in cpuset"); break; case CONSTRAINT_NONE: retry: /* * Rambo mode: Shoot down a process and hope * issues we may have. */ p = select_bad_process(&points); if (PTR_ERR(p) == -1UL) goto out; /* Found nothing?!?! Either we hang or we panic. */ - 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