In <E127N4e-00028P-00@the-village.bc.nu> Alan Cox (alan@lxorguk.ukuu.org.uk) wrote:
>> It's joke, right ? This particular problem is known for more then year, was
>> discussed MANY times @ linux-kernel and still there are no solution in
>> mainstream kernel :-((
AC> I know no single Unix like OS I can't bring down if I dont have resource limiting.
AC> Also for that matter Ive yet to meet one I can't kill even with resource limiting
AC> in place.
Hmm. Perhaps... On other hand Sebastian saying:
-- cut --
Oh, I didn't knew that. I know that this is no common malloc() bomb
problem, and we haven't heard about it, so we want to make it public, even
if it is known to the kernel developers. A bit pressure to the admins side
could not be wrong to use resource limits.
Btw, any BSD we tried on doesn't suffer from this or similar problems.
-- cut --
Who is on drugs ?
AC> Feel free to fix it.
>> P.S. Oh and it's not all story: you can use SysV shared memory support to make
>> exploit usable even if admin limited your memory usage ! It's also well-known
>> problem without solution in mainstream kernel :-(
AC> The total amount of shared memory is configurable on Linux 2.2.x
-
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/
This archive was generated by hypermail 2b29 : Sat Jan 15 2000 - 21:00:14 EST