From: g@0xff.cl
To: Valdis.Kletnieks@vt.edu
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Reserve N process to root
Date: Wed, 10 Oct 2007 14:02:54 -0700 (PDT) [thread overview]
Message-ID: <56055.190.54.55.123.1192050174.squirrel@webmail.0xff.cl> (raw)
In-Reply-To: <27658.1192045814@turing-police.cc.vt.edu>
> On Wed, 10 Oct 2007 09:46:22 EDT, Gustavo Chain said:
>> El Wed, 10 Oct 2007 15:14:06 +0930
>> David Newall <david@davidnewall.com> escribió:
>> > That was what I thought you had in mind; it protects from some kind
>> > of fork bomb, right? But it doesn't seem useful unless you guarantee
>> > having a process already running (with CAP_SYS_ADMIN) *before* the
>> > bomb goes off.
>>
>> Not really, because fork bomb will never reach maximum pid possible.
>> And root will always have a "slot" to kill desired processes.
>
> 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).
>
> Many distros will leave a /sbin/mingetty running on tty1 through tty6, and
> you *can* use those to get a root shell. David's point is that without
> something like that already in place, the patch doesn't help....
>
>
but once you are logged in, how can you "spawn" processes (ps, kill, and
so on) if the limit is reached ?
next prev parent reply other threads:[~2007-10-10 21:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 23:48 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 [this message]
2007-10-11 0:05 ` David Newall
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=56055.190.54.55.123.1192050174.squirrel@webmail.0xff.cl \
--to=g@0xff.cl \
--cc=Valdis.Kletnieks@vt.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®