From: Al Viro <viro@ZenIV.linux.org.uk>
To: Raymond Jennings <shentino@gmail.com>
Cc: 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 07:43:48 +0000 [thread overview]
Message-ID: <20130216074348.GC4503@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAGDaZ_oSzQOLsoeWQFNQ8R5-NBKPAUygvjvzvef9q40WBu1sWw@mail.gmail.com>
On Fri, Feb 15, 2013 at 11:20:18PM -0800, Raymond Jennings wrote:
> An even bigger question might be why an execve is allowed to get into
> an unrecoverable state to begin with. Assuming that one builds the
> new mm_struct and whatnot BEFORE discarding old state, why would
> execve be in a position for a fatal error in the first place?
When would you kill the rest of thread group? Take a look at de_thread() -
we are not just replacing ->mm during execve(). Signal delivery logics,
etc.
next prev parent reply other threads:[~2013-02-16 7:43 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
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 [this message]
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=20130216074348.GC4503@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=shentino@gmail.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.