public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul@openvz.org>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Andi Kleen <andi@firstfloor.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Herbert Poetzl <herbert@13thfloor.at>,
	Krzysztof Halasa <khc@pm.waw.pl>, Pavel Machek <pavel@ucw.cz>,
	"Serge E. Hallyn" <serue@us.ibm.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Roland McGrath <roland@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ptrace: allow to ptrace /sbin/init
Date: Thu, 27 Mar 2008 10:20:20 +0300	[thread overview]
Message-ID: <47EB4AB4.7070704@openvz.org> (raw)
In-Reply-To: <20080326201623.GA131@tv-sign.ru>

Oleg Nesterov wrote:
> Afaics, currently there are no kernel problems with ptracing init, it can't
> lose SIGNAL_UNKILLABLE flag and be killed/stopped by accident.
> 
> The ability to strace/debug init can be very useful if you try to figure
> out why it does not work as expected.
> 
> However, admin should know what he does, "gdb /sbin/init 1" stops init, it
> can't reap orphaned zombies or take care of /etc/inittab until continued.
> It is even possible to crash init (and thus the whole system) if you wish,
> ptracer has full control.
> 
> See also the long discussion: http://marc.info/?t=120628018600001
> 
> Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>

Acked-by: Pavel Emelyanov <xemul@openvz.org>

      parent reply	other threads:[~2008-03-27  7:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 20:16 [PATCH] ptrace: allow to ptrace /sbin/init Oleg Nesterov
2008-03-26 20:40 ` Roland McGrath
2008-03-27  7:20 ` Pavel Emelyanov [this message]

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=47EB4AB4.7070704@openvz.org \
    --to=xemul@openvz.org \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=ebiederm@xmission.com \
    --cc=herbert@13thfloor.at \
    --cc=khc@pm.waw.pl \
    --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=serue@us.ibm.com \
    /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