From: Florian Weimer <fw@deneb.enyo.de>
To: Andreas Schwab <schwab@suse.de>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] Use execveat syscall in fexecve
Date: Thu, 07 Sep 2017 11:27:00 -0000 [thread overview]
Message-ID: <87bmmmlpe1.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <mvm8thqdgj1.fsf@suse.de> (Andreas Schwab's message of "Thu, 07 Sep 2017 11:06:26 +0200")
* Andreas Schwab:
> By using execveat we no longer depend on /proc. The execveat syscall was
> introduced in 3.19, except for a few late comers.
Ideally, this should have a test that executing “/bin/sh -c true”
works, both with an O_PATH descriptor and a regular descriptor.
The implementation itself (including the AT_EMPTY_PATH flag) and the
__ASSUME_EXECVEAT conditions look good to me.
next prev parent reply other threads:[~2017-09-07 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 9:06 Andreas Schwab
2017-09-07 11:27 ` Florian Weimer [this message]
2017-09-11 10:23 ` [PATCH v2] " Andreas Schwab
2017-09-11 20:30 ` Adhemerval Zanella
2017-09-11 20:38 ` Joseph Myers
2017-09-11 20:59 ` Florian Weimer
2017-09-11 22:58 ` Adhemerval Zanella
2017-09-14 8:05 ` Andreas Schwab
2017-09-14 13:44 ` Adhemerval Zanella
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=87bmmmlpe1.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).