From: Pedro Alves <palves@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
pacman@kosh.dhis.org, linux-man <linux-man@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Denys Vlasenko <dvlasenk@redhat.com>, Tejun Heo <tj@kernel.org>,
Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: ptrace.2: PTRACE_KILL needs a stopped process too
Date: Wed, 09 May 2012 23:16:05 +0100 [thread overview]
Message-ID: <4FAAECA5.8050606@redhat.com> (raw)
In-Reply-To: <20120509211429.GA2455@redhat.com>
On 05/09/2012 10:14 PM, Oleg Nesterov wrote:
>> i like to assume that my code isn't going to be bug free, so the more
>> mechanisms i have in place to protect innocent bystanders the better :)
>> -mike
>
> From this pov PTRACE_KILL is safer, I agree ;)
Yeah, until you trip on that case where it resumes the process
instead of killing it... At that point, it's useless.
Since I know Mike likes hacking on GDB so much ;-), FYI, this is
exercised by the gdb.base/kill-after-signal.exp test.
--
Pedro Alves
next prev parent reply other threads:[~2012-05-09 22:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091216004533.22261.qmail@kosh.dhis.org>
2012-04-22 18:56 ` ptrace.2: PTRACE_KILL needs a stopped process too Michael Kerrisk (man-pages)
2012-04-22 20:04 ` Oleg Nesterov
2012-05-02 12:06 ` Pedro Alves
2012-05-09 15:09 ` Mike Frysinger
2012-05-09 19:35 ` Pedro Alves
2012-05-09 20:12 ` Oleg Nesterov
2012-05-09 16:41 ` Mike Frysinger
2012-05-09 21:14 ` Oleg Nesterov
2012-05-09 22:16 ` Pedro Alves [this message]
2012-05-09 22:08 ` Pedro Alves
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=4FAAECA5.8050606@redhat.com \
--to=palves@redhat.com \
--cc=dvlasenk@redhat.com \
--cc=jan.kratochvil@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=oleg@redhat.com \
--cc=pacman@kosh.dhis.org \
--cc=tj@kernel.org \
--cc=vapier@gentoo.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