I only have one question about this scheme. What about a program that
leaks very slowly over a long period of time? (Wasn't there even a kernel
leak like that in the early 2.2.x series?) It will eventually end up
exausting all memory and surely there'll be another program asking for
memory faster than it as you head the OOM situation.
I know, I know, this is a rare case and the program doing that should be
fixed. But it is something to think about. Perhaps there'll be a new
class of attacks, ones that take weeks or months to pull off.
On Fri, 7 Jul 2000, Derek Martin wrote:
> Based on what others have said in this thread, it sounds to me like the
> right answer is for the kernel to do something like keep track of how fast
> each process is allocating/using memory, and kill the highest users. And
> it also sounds like that's in the works. So I'll shut up now... :)
--
Two penguins were walking on an iceburg. The first one said to the
second, "you look like you are wearing a tuxedo." The second one said,
"I might be..."
--David Lynch, Twin Peaks
-
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 : Fri Jul 07 2000 - 21:00:21 EST