Messages in this thread | | | Date | Mon, 26 Mar 2001 11:01:07 +0100 | From | Jonathan Morton <> | Subject | Re: [PATCH] Prevent OOM from killing init |
| |
>> I'm currently investigating the old non-overcommit patch, which (apart from >> needing manual applying to recent kernels) appears to be rather broken in a >> trivial way. It prevents allocation if total reserved memory is greater >> than the total unallocated memory. Let me say that again, a different way >> - it prevents memory usage from exceeding 50%... > >Think fork(2).
fork() is allowed to return a failure value, and it already does so if there isn't enough memory (at least with the limited tests I've come up with). Guess again.
I have, however, found a bug in the non-overcommit patch - it seems to be capable of double-freeing (and then some) - starting 4 Java VMs and then closing them causes VMReserved to go negative on my system.
-------------------------------------------------------------- from: Jonathan "Chromatix" Morton mail: chromi@cyberspace.org (not for attachments) big-mail: chromatix@penguinpowered.com uni-mail: j.d.morton@lancaster.ac.uk
The key to knowledge is not to rely on people to teach you it.
Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/
-----BEGIN GEEK CODE BLOCK----- Version 3.12 GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*) -----END GEEK CODE BLOCK-----
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |