Re: [2.4.18] Security: Process-Killer if machine get's out of memory

dean gaudet (
Tue, 26 Mar 2002 12:24:58 -0800 (PST)

On Sun, 24 Mar 2002, Alan Cox wrote:

> > > My system cannot (short of a bug) go OOM. Thats what the new overcommit
> > > mode 2/3 ensures
> >
> > How does a process react that doesn't get no more memory?
> Thats up to the process. If a program doesn't handle malloc/mmap/etc
> failures then its junk anyway

what's the point if you're just going to get signal delivery when you
least want it, even when malloc returns non-NULL? it could even be due to
stack growth which the compiler is under control of and has no exception
mechanism available. i personally prefer to take the signal and exit,
it's guaranteed to work in all cases. (hence, apache-1.3 and other
multiprocess daemon superiority over threaded and event-driven code, tee
hee :)


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at