Re: [RFC] SIGKILL vs. SIGSEGV on late execve() failures

[Al Viro]

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/