Re: Out Of Memory in v. 2.1

Stefan Monnier (monnier+lists/linux/kernel/news/@TEQUILA.SYSTEMSZ.CS.YALE.EDU)
06 Oct 1998 11:37:40 -0400


>>>>> "Albert" == Albert D Cahalan <acahalan@cs.uml.edu> writes:
>> Stefan writes:
>>> Turning off overcommitment doesn't save you from figuring out
>>> what to do when you run out of memory (return NULL from malloc
> Have /sbin/init disable overcommit on itself after swap is on.

Reread what I wrote. Even if there is no overcommitment of any form anywhere
on your system, you might run out of memory (sound obvious enough I hope)
in which case malloc (for instance) might return NULL. If this malloc was
executed by /sbin/init, it might very well end up rebooting the machine.

Stefan

PS: and even if /sbin/init doesn't do any memory allocation of any form
(whether via malloc or via stack-growing), the same problem applies to other
important processes.

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