linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jann Horn <jann-XZ1E9jl8jIdeoWH0uzbU5w@public.gmane.org>
To: Steven Stewart-Gallus
	<sstewartgallus00-QKvm5KDIoDa7M0a00MdBSQ@public.gmane.org>
Cc: linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: execve is not atomic, what is the exit state of the process when execve fails after throwing away the original process image?
Date: Sat, 3 May 2014 19:45:10 +0200	[thread overview]
Message-ID: <20140503174510.GA7720@debjann.fritz.box> (raw)
In-Reply-To: <faa2c0e82f8a8.536300c8-BTv7Ps/Sm75C8prJL3GQQw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 342 bytes --]

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?

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2014-05-03 17:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02  2:19 execve is not atomic, what is the exit state of the process when execve fails after throwing away the original process image? Steven Stewart-Gallus
     [not found] ` <faa2c0e82f8a8.536300c8-BTv7Ps/Sm75C8prJL3GQQw@public.gmane.org>
2014-05-03 17:45   ` Jann Horn [this message]
     [not found]     ` <20140503174510.GA7720-7cfQGs147y6a6lf8Wg2v7Z5kstrrjoWp@public.gmane.org>
2014-05-03 22:18       ` Steven Stewart-Gallus
     [not found]         ` <faa0c9e9297ad.53656b4c-BTv7Ps/Sm75C8prJL3GQQw@public.gmane.org>
2014-05-04 19:27           ` Michael Kerrisk (man-pages)
     [not found]             ` <53669485.3020007-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-05-04 20:15               ` Michael Kerrisk (man-pages)

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=20140503174510.GA7720@debjann.fritz.box \
    --to=jann-xz1e9jl8jideowh0uzbu5w@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sstewartgallus00-QKvm5KDIoDa7M0a00MdBSQ@public.gmane.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;
as well as URLs for NNTP newsgroup(s).