From: Chris Atenasio <root@lilo.dyn.ml.org>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Nicolas Devillard <ndevilla@mygale.org>,
linux-mm@kvack.org, Alan Cox <number6@the-village.bc.nu>
Subject: Re: memory overcommitment
Date: Tue, 18 Aug 1998 11:52:06 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.00.9808181124250.6395-100000@chris.atenasio.net> (raw)
In-Reply-To: <199808171833.TAA03492@dax.dcs.ed.ac.uk>
> If you can suggest a good algorithm for selecting processes to kill,
> we'd love to hear about it. The best algorithm will not be the same for
> all users.
How bout: if(no_more_ram) kill(process_using_most_ram());
Of course to be useful it would have to add together the usage of multiple
instances of a program of the same uid(and then kill all of them too!).
Furthermore you might even want to kill uid 0 progs last. This way hopefully an
attacker mallocing way too much or starting a fork bomb would be the one that
gets shafted. (Maybe even write an interface to pass the offending uid to a
userspace program which can then invalidate that user account, send mail, do
cool things etc.) Then what if you(the admin)C do something evil?
Well... don't!
- Chris
--------------------------------------------------------------------------------
Chris Atenasio (chrisa@ultranet.com) -- Friends dont let friends use Windows.
Send me mail with subject "send pgp key" or "word of the day" for autoresponse.
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1998-08-18 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-17 8:46 Nicolas Devillard
1998-08-17 18:33 ` Stephen C. Tweedie
1998-08-18 15:52 ` Chris Atenasio [this message]
1998-08-19 12:08 ` Stephen C. Tweedie
1998-08-18 16:34 ` Nicolas Devillard
1998-08-19 12:07 ` Stephen C. Tweedie
1998-08-19 17:17 ` Nicolas Devillard
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=Pine.LNX.4.00.9808181124250.6395-100000@chris.atenasio.net \
--to=root@lilo.dyn.ml.org \
--cc=chrisa@ultranet.com \
--cc=linux-mm@kvack.org \
--cc=ndevilla@mygale.org \
--cc=number6@the-village.bc.nu \
--cc=sct@redhat.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