public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tonnerre <tonnerre@thundrix.ch>
To: Thomas Habets <thomas@habets.pp.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] oom_pardon, aka don't kill my xlock
Date: Thu, 23 Sep 2004 14:24:28 +0200	[thread overview]
Message-ID: <20040923122428.GA8816@thundrix.ch> (raw)
In-Reply-To: <200409230857.57145.thomas@habets.pp.se>

[-- Attachment #1: Type: text/plain, Size: 854 bytes --]

Salut,

On Thu, Sep 23, 2004 at 08:57:50AM +0200, Thomas Habets wrote:
> Yup. What would be a good interface for setting that flag per-process? 
> prctl()?
> Personally, I'd prefer it without userspace having to write code for it.

Well, either  via a  new syscall/ioctl, or  via some exported  file in
/proc or /sys. I guess the second approach (file) will be prefered.

> Also, it should be able to protect against a DoS where a user launches N 
> un-OOM-killable processes.

You can still  do that. Maybe kill those processes  first who got less
criterias matching the OOM gracefulness, so you can protect httpd more
strongly than xlock.

Also remember to set per-user limits of processes. :)

> > What about programs with spaces in its names?
> 
> I thought "screw 'em". :-)

Now that's what I call policy!

			    Tonnerre

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-09-23 12:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-22 23:23 [PATCH] oom_pardon, aka don't kill my xlock Thomas Habets
2004-09-23  0:01 ` Nick Piggin
2004-09-23  0:07 ` William Lee Irwin III
2004-09-23  4:45 ` Tonnerre
2004-09-23  6:57   ` Thomas Habets
2004-09-23 12:24     ` Tonnerre [this message]
2004-09-23 13:32       ` Thomas Habets
2004-09-23 23:45 ` Andries Brouwer
2004-09-24 13:19   ` Alan Cox
2004-09-24 19:58     ` Thomas Habets
2004-09-24 21:15       ` Alan Cox
2004-09-25 10:08         ` Thomas Habets
2004-09-27 10:41         ` Marcelo Tosatti
2004-09-27 12:54           ` Lars Marowsky-Bree
2004-09-27 13:12             ` Jon Masters
2004-09-27 12:36               ` Alan Cox
2004-09-27 13:35               ` Marcelo Tosatti
2004-09-27 15:59                 ` Jon Masters
2004-09-27 17:12                 ` Herbert Poetzl
2004-09-27 16:42                   ` Marcelo Tosatti
2004-09-28 13:33                     ` Herbert Poetzl
2004-09-28 12:32                       ` Marcelo Tosatti
2004-09-28 23:55                         ` Herbert Poetzl
2004-09-27 23:07                   ` Jon Masters
2004-09-29  0:49           ` Andries Brouwer
2004-09-24 14:07   ` Pavel Machek
2004-09-24 22:57   ` Jon Masters
2004-09-25 16:32 ` Andrea Arcangeli
  -- strict thread matches above, loose matches on Subject: below --
2004-09-27 12:00 Thomas Habets
2004-09-27 12:17 ` Jon Masters

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=20040923122428.GA8816@thundrix.ch \
    --to=tonnerre@thundrix.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@habets.pp.se \
    /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