Thank you Jann Horn. http://lxr.free-electrons.com/source/fs/binfmt_elf.c#L740 answers my question. On reflection, the kernel code makes sense. The process must either exit with an error code or raise the SIGKILL signal because SIGKILL and SIGSTOP are the only unblockable signals (of course, the kernel has the privileges to do whatever it wants but it tries to be consistent with userspace). Strangely, in other places the SIGSEGV is sent when the ELF file is incorrect in some places and I don't fully understand that part of the code. Still, I understand enough to look at the code in more detail later. Thank you, Steven Stewart-Gallus P.S. I'm CC'ing Michael because he wanted to know this case so could document it. ----- Original Message ----- From: Jann Horn <jann@xxxxxxxxx> Date: Saturday, May 3, 2014 10:45 am Subject: Re: execve is not atomic, what is the exit state of the process when execve fails after throwing away the original process image? To: Steven Stewart-Gallus <sstewartgallus00@xxxxxxxxxxxxxxx> Cc: linux-api@xxxxxxxxxxxxxxx > On Fri, May 02, 2014 at 02:19:52AM +0000, Steven Stewart-Gallus wrote: > > execve is not atomic, what is the exit state of the process when > > execve fails after throwing away the original process image? > > See http://lxr.free-electrons.com/source/fs/binfmt_elf.c#L740 or > so – as far as I know, the kernel sends a SIGKILL. Does that help? > -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
