Messages in this thread | | | Date | Thu, 12 Oct 2000 14:21:23 +1100 | From | Matthew Hawkins <> | Subject | Re: [PATCH] OOM killer API (was: [PATCH] VM fix for 2.4.0-test9 & OOM handler) |
| |
On 2000-10-11 19:53:50 -0700, lamont@icopyright.com wrote: > On other machines I'd set RLIMIT_DATA and my OOM problems went away, > but on linux this didn't work
RLIMIT_DATA appears to only be checked for aout format executables. Looking at the 2.4.0-test10pre1 sources for fs/binfmt_aout.c and fs/binfmt_elf.c you'll note the difference in load_aout_binary() and load_elf_binary(), both just above the comment of "OK, This is the point of no return"
Does putting a similar check to the aout one make sense for ELF?
I'm just trying to avoid Rik having to pull his hair out implementing a system that conceptually already exists in the kernel (nasty processes being terminated before they do some damage). Especially when that existing system is far more configurable.
Cheers,
-- Matt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |