From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Shentino <shentino@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] SIGKILL vs. SIGSEGV on late execve() failures
Date: Sat, 16 Feb 2013 00:38:15 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.03.1302160021490.10334@linux-mips.org> (raw)
In-Reply-To: <20130216000435.GY4503@ZenIV.linux.org.uk>
On Sat, 16 Feb 2013, Al Viro wrote:
> > > + send_sig(SIGSEGV, current, 0);
> >
> > This might be a stupid miscue on my part, but shouldn't it be
> > force_sig instead of send_sig?
> >
> > I've got this crazy hunch that having SEGV masked might muck something up.
>
> How would you manage to have it masked at that point? setup_new_exec()
> is inevitable after success of flush_old_exec() and it will do
> flush_signal_handlers() for us.
So just to be completely safe here -- is your proposed change going to
affect processes being traced anyhow? E.g. won't GDB see some sort of a
limbo state when the child is terminated this way? According to ptrace(2)
man page SIGKILL is the only exception to the usual child signal trapping
policy.
Maciej
next prev parent reply other threads:[~2013-02-16 0:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 5:36 [RFC] SIGKILL vs. SIGSEGV on late execve() failures Al Viro
2013-02-15 20:02 ` Linus Torvalds
2013-02-15 21:59 ` Al Viro
2013-02-15 23:12 ` Shentino
2013-02-16 0:04 ` Al Viro
2013-02-16 0:38 ` Maciej W. Rozycki [this message]
2013-02-16 0:38 ` Shentino
2013-02-16 0:46 ` Shentino
2013-02-16 1:50 ` Al Viro
2013-02-16 2:20 ` Al Viro
2013-02-16 7:20 ` Raymond Jennings
2013-02-16 7:43 ` Al Viro
2013-02-16 8:13 ` Raymond Jennings
2013-02-16 0:40 ` Linus Torvalds
2013-02-16 1:22 ` Al Viro
2013-02-16 1:44 ` Linus Torvalds
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=alpine.LFD.2.03.1302160021490.10334@linux-mips.org \
--to=macro@linux-mips.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shentino@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).