All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Newall <david@davidnewall.com>
To: Valdis.Kletnieks@vt.edu
Cc: Gustavo Chain <g@0xff.cl>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Reserve N process to root
Date: Thu, 11 Oct 2007 09:35:46 +0930	[thread overview]
Message-ID: <470D68DA.2010803@davidnewall.com> (raw)
In-Reply-To: <27658.1192045814@turing-police.cc.vt.edu>

Valdis.Kletnieks@vt.edu wrote:
> What David meant was that "root will always have a slot" doesn't *actually*
> help unless you *also* have a way to actually *spawn* such a process.  In order
> to do the ps, kill, and so on that you need to recover, you need to already
> have either a root shell available, or a way to *get* a root shell that doesn't
> rely on a non-root process (so /bin/su doesn't help here).

That's right, although it's worse than that.  You need to have a process 
with CAP_SYS_ADMIN.  If root processes normally have that capability 
then the reserved slots may well disappear before you notice a problem.  
If root processes normally don't have it, then you need to guarantee 
that one is already running.

  parent reply	other threads:[~2007-10-11  0:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09 23:48 [PATCH] Reserve N process to root Gustavo Chain
2007-10-10  1:49 ` David Newall
2007-10-10  5:15   ` Gustavo Chain
2007-10-10  5:44     ` David Newall
2007-10-10 13:46       ` Gustavo Chain
2007-10-10 14:13         ` David Newall
2007-10-10 19:50         ` Valdis.Kletnieks
2007-10-10 21:02           ` g
2007-10-11  0:05           ` David Newall [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-11 21:02 Al Boldi
2007-10-12  2:42 ` Kyle Moffett
2007-10-12  5:37   ` Al Boldi
2007-10-12  5:49     ` Kyle Moffett
2007-10-12  6:29       ` Al Boldi
2007-10-13  1:34         ` Gustavo Chain
2007-10-13  5:01           ` Al Boldi

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=470D68DA.2010803@davidnewall.com \
    --to=david@davidnewall.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=g@0xff.cl \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.