From: pavel-velo@bug.ucw.cz
To: Szabolcs Szakacsits <szaka@f-secure.com>,
Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Linus Torvalds <torvalds@transmeta.com>,
Ingo Molnar <mingo@elte.hu>
Subject: RE: KPATCH] Reserve VM for root (was: Re: Looking for better VM)
Date: Wed, 1 Jan 1997 22:21 -0800 [thread overview]
Message-ID: <200011142012.VAA00150@bug.ucw.cz> (raw)
Hi!
>I've also never said OOM killer should be disabled. In theory the
>non-overcommitting systems deadlock, Linux survives. Ironically
>usually it's just the opposite in practice. Any user can
>deadlock/crash Linux [default install, no quotas] but not an
>non-overcommitting system [root can clean up]. Here is an example code
>"simulating" a leaking daemon that will "deadlock" Linux even with
>your OOM killer patch [that is anyway *MUCH* better than the actually
>non-existing one in 2.2.x kernels]:
>
>main() { while(1) if (fork()) malloc(1); }
>
>With the patch below I could ssh to the host and killall the offending
>processes. To enable reserving VM space for root do
what about main() { while(1) system("ftp localhost &"); }
This. or so,ething similar should allow you to kill your machine even with your
patch from normal user account
Pavel
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next reply other threads:[~1997-01-02 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-02 6:21 pavel-velo [this message]
2000-11-16 15:01 ` Szabolcs Szakacsits
2000-11-16 15:51 ` Rik van Riel
2000-11-16 16:03 ` Christoph Hellwig
2000-11-16 16:05 ` Rik van Riel
2000-11-16 21:33 ` Szabolcs Szakacsits
2000-11-18 20:49 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200011142012.VAA00150@bug.ucw.cz \
--to=pavel-velo@bug.ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=riel@conectiva.com.br \
--cc=szaka@f-secure.com \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox