From: Oleg Nesterov <oleg@tv-sign.ru>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: ebiederm@xmission.com, xemul@openvz.org, pavel@ucw.cz,
sds@tycho.nsa.gov, roland@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ptrace: it is fun to strace /sbin/init
Date: Tue, 25 Mar 2008 01:56:11 +0300 [thread overview]
Message-ID: <20080324225611.GA157@tv-sign.ru> (raw)
In-Reply-To: <20080324152906.dee7b272.akpm@linux-foundation.org>
On 03/24, Andrew Morton wrote:
>
> On Sun, 23 Mar 2008 16:51:10 +0300
> Oleg Nesterov <oleg@tv-sign.ru> wrote:
>
> > Ptracing of /sbin/init is not allowed. Of course, this is dangerous, but may
> > be useful. Introduce the kernel boot parameter to allow this, so that we can't
> > surprise some special/secured systems.
>
> I dunno, is this really needed?
Well, this is the question. I think it would be very nice to have the ability
to debug/strace init. Especially if you try to make your own distribution /
your own init.
Sometimes I see init at the top of the top's output, with this patch I have a
chance to see what's going on on my system.
> If root wants to screw up his kernel then
> he is free to do so.
I think you and Pavel are very wrong here.
First, this has nothing to do with kernel, imho. Afaics, now there are no kernel
problems with ptracing init.
And. When I was admin in my previous life, I certainly was not able to patch
the kernel and then strace/debug init.
> And if we *really* want an extra foot-protector for this, it could be a
> runtime /proc/sys/kernel/root-can-shoot-inits-foot rather than a boot-time
> option?
Even better! I agree, will re-send. I choose the boot-time paramater because
it looks like the "most safe" option.
Oleg.
next prev parent reply other threads:[~2008-03-24 23:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 13:51 [PATCH] ptrace: it is fun to strace /sbin/init Oleg Nesterov
2008-03-24 16:01 ` Pavel Machek
2008-03-24 16:40 ` Oleg Nesterov
2008-03-24 22:39 ` Pavel Machek
2008-03-24 23:04 ` Oleg Nesterov
2008-03-24 23:09 ` Pavel Machek
2008-03-24 23:18 ` Oleg Nesterov
2008-03-24 23:26 ` Andrew Morton
2008-03-24 23:38 ` Oleg Nesterov
2008-03-25 12:03 ` Stephen Smalley
2008-03-25 13:40 ` Serge E. Hallyn
2008-03-25 14:37 ` Stephen Smalley
2008-03-25 18:06 ` Serge E. Hallyn
2008-03-25 19:07 ` Herbert Poetzl
2008-03-25 21:55 ` Pavel Machek
2008-03-26 15:31 ` Andrew Morgan
2008-03-26 15:47 ` Pavel Emelyanov
2008-03-24 22:29 ` Andrew Morton
2008-03-24 22:56 ` Oleg Nesterov [this message]
2008-03-24 23:08 ` Andrew Morton
2008-03-24 23:29 ` Oleg Nesterov
2008-03-25 10:00 ` Andi Kleen
2008-03-25 14:16 ` Krzysztof Halasa
2008-03-25 14:22 ` Andi Kleen
2008-03-25 14:30 ` Krzysztof Halasa
2008-03-25 14:35 ` Andi Kleen
2008-03-25 14:58 ` Krzysztof Halasa
2008-03-25 14:47 ` Pavel Machek
2008-03-25 14:56 ` Andi Kleen
2008-03-25 17:42 ` Oleg Nesterov
2008-03-25 22:00 ` Roland McGrath
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=20080324225611.GA157@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=roland@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=xemul@openvz.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