From: Krzysztof Halasa <khc@pm.waw.pl>
To: Andi Kleen <andi@firstfloor.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Oleg Nesterov <oleg@tv-sign.ru>,
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 15:16:13 +0100 [thread overview]
Message-ID: <m3fxuedh3m.fsf@maximus.localdomain> (raw)
In-Reply-To: <87r6dzi0mw.fsf@basil.nowhere.org> (Andi Kleen's message of "25 Mar 2008 11\:00\:39 +0100")
Andi Kleen <andi@firstfloor.org> writes:
> It would be fine to allow this unconditionally if there was some mechanism
> to make sure someone else takes over reaping childs while init is
> ptraced.
Well, I think it isn't even necessary, unless you ptrace init for a
long time. I would simply go with the simple 1-line patch.
> I like the general idea -- i used to patch kernels to allow this too,
> but it is dangerous.
Though root-only. Root doesn't want to be limited and knows better
anyway. I think ptracing init is useful even when no one takes care
of the dead (especially if you want to trace waits).
--
Krzysztof Halasa
next prev parent reply other threads:[~2008-03-25 14:16 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
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 [this message]
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=m3fxuedh3m.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--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