From: Oleg Nesterov <oleg@tv-sign.ru>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Pavel Emelyanov <xemul@openvz.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ptrace: it is fun to strace /sbin/init
Date: Tue, 25 Mar 2008 02:18:59 +0300 [thread overview]
Message-ID: <20080324231859.GA193@tv-sign.ru> (raw)
In-Reply-To: <20080324230930.GE2426@elf.ucw.cz>
On 03/25, Pavel Machek wrote:
>
> On Tue 2008-03-25 02:04:58, Oleg Nesterov wrote:
> > On 03/24, Pavel Machek wrote:
> > >
> > > > /sbin/init is important, but there are other important (and sometimes
> > > > much more important) services. Why it is so special so that we can't
> > > > debug/strace it?
> > >
> > > Maybe. Let's kill /sbin/init protection in 2.6.26. But making it
> > > optional is wrong.
> >
> > You are right, the boot parameter is silly. How about sysctl?
>
> I'd prefer it to be hardcoded, really.
Yes! me too.
> "You can kill /sbin/init" sounds right.
>
> "You can kill /sbin/init on 2.6.26+" sounds... still quite ok.
>
> "You can kill /sbin/init on 2.6.26+ if you have /proc/sys/foo/bar ==
> 1" sounds... quite wrong.
Please look at another discussion, http://marc.info/?t=120568298600007
When I did this simple patch, I was very sure it is "obviously good".
But as Stephen pointed out, we have the systems that relies on the
current behaviour, even if this behaviour is not "optimal".
Oleg.
next prev parent reply other threads:[~2008-03-24 23:20 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 [this message]
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
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=20080324231859.GA193@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