From: Pedro Alves <palves@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Amnon Shiloh <u3557@miso.sublimeip.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Serge Hallyn <serge.hallyn@canonical.com>,
Chris Evans <scarybeasts@gmail.com>,
David Howells <dhowells@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>,
u3557@dialix.com.au, security@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: PT_EXITKILL (Was: pdeath_signal)
Date: Thu, 08 Nov 2012 13:00:48 +0000 [thread overview]
Message-ID: <509BAD00.9060600@redhat.com> (raw)
In-Reply-To: <20121108124424.GB20917@redhat.com>
On 11/08/2012 12:44 PM, Oleg Nesterov wrote:
> On 11/08, Pedro Alves wrote:
>> If this isn't inherited by the ptrace child's children, a fork child can
>> end up detached if the tracer dies before it had a chance of setting
>> the PTRACE_O_EXITKILL on the new auto-attached child.
>
> It is copied like the other options.
Oh, you're right. I got confused - GDB has code to always set options
on the fork children after PTRACE_EVENT_(V)FORK. Dunno where that came from.
>> Which sounds like another argument for PTRACE_O_INHERIT, as in:
>> http://sourceware.org/ml/archer/2011-q1/msg00026.html
>
> The point of PTRACE_O_INHERIT would be to attach newly-created threads and
> children without causing an event stop and the attendant overhead.
>
> this is another thing, I guess.
Yes, yes.
--
Pedro Alves
prev parent reply other threads:[~2012-11-08 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121106152050.GA18218@sergelap>
[not found] ` <20121106201428.9D72959201A@miso.sublimeip.com>
2012-11-07 15:09 ` Oleg Nesterov
2012-11-08 6:29 ` Amnon Shiloh
2012-11-08 12:37 ` Oleg Nesterov
2012-11-08 13:03 ` Amnon Shiloh
2012-11-18 20:21 ` [PATCH 0/1] ptrace: introduce PTRACE_O_EXITKILL Oleg Nesterov
2012-11-18 20:21 ` [PATCH 1/1] " Oleg Nesterov
2012-11-08 12:48 ` PF_NO_SIGSTOP (Was: PT_EXITKILL) Oleg Nesterov
2012-11-08 14:05 ` Amnon Shiloh
2012-11-08 12:16 ` PT_EXITKILL (Was: pdeath_signal) Pedro Alves
2012-11-08 12:44 ` Oleg Nesterov
2012-11-08 13:00 ` Pedro Alves [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=509BAD00.9060600@redhat.com \
--to=palves@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dvlasenk@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=oleg@redhat.com \
--cc=scarybeasts@gmail.com \
--cc=security@kernel.org \
--cc=serge.hallyn@canonical.com \
--cc=u3557@dialix.com.au \
--cc=u3557@miso.sublimeip.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
Powered by JetHome