From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Rich Felker <dalias-/miJ2pyFWUyWIDz0JBNUog@public.gmane.org>
Cc: linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"Joseph S. Myers"
<joseph-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org>,
libc-alpha-9JcytcrH/bA+uJoB2kUjGw@public.gmane.org
Subject: Re: Request for comments: reserving a value for O_SEARCH and O_EXEC
Date: Tue, 6 Aug 2013 17:54:15 +0200 [thread overview]
Message-ID: <20130806155415.GA12926@lst.de> (raw)
In-Reply-To: <20130806152316.GW221-C3MtFaGISjmo6RMmaWD+6Sb1p8zYI1N1@public.gmane.org>
On Tue, Aug 06, 2013 at 11:23:16AM -0400, Rich Felker wrote:
> > For that we'd also want to move fexec(ve) into the kernel space.
>
> I agree this would be useful, but it's a separate issue.
I don't think it is. The whole point of O_EXEC is to support fexecve.
Without moving it to kernel I can't see how you can make it strictly
conforming to this requirement in Posix that the file descriptor
must be valid for executing.
Fortunately enough the kernel implementation is trivial.
next prev parent reply other threads:[~2013-08-06 15:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 22:25 Request for comments: reserving a value for O_SEARCH and O_EXEC Rich Felker
2013-08-06 5:54 ` Christoph Hellwig
[not found] ` <20130806055425.GA9280-jcswGhMUV9g@public.gmane.org>
2013-08-06 13:42 ` Rich Felker
2013-08-06 14:03 ` Christoph Hellwig
[not found] ` <20130806140321.GA4421-jcswGhMUV9g@public.gmane.org>
2013-08-06 14:36 ` Rich Felker
[not found] ` <20130806143609.GV221-C3MtFaGISjmo6RMmaWD+6Sb1p8zYI1N1@public.gmane.org>
2013-08-06 14:51 ` Christoph Hellwig
[not found] ` <20130806145159.GA8192-jcswGhMUV9g@public.gmane.org>
2013-08-06 15:23 ` Rich Felker
[not found] ` <20130806152316.GW221-C3MtFaGISjmo6RMmaWD+6Sb1p8zYI1N1@public.gmane.org>
2013-08-06 15:53 ` Joseph S. Myers
2013-08-06 15:54 ` Christoph Hellwig [this message]
[not found] ` <20130806155415.GA12926-jcswGhMUV9g@public.gmane.org>
2013-08-06 16:30 ` Rich Felker
-- strict thread matches above, loose matches on Subject: below --
2013-08-03 2:48 Rich Felker
[not found] ` <20130803024808.GA26932-C3MtFaGISjmo6RMmaWD+6Sb1p8zYI1N1@public.gmane.org>
2013-08-12 17:42 ` Andy Lutomirski
2013-08-12 17:42 ` Andy Lutomirski
[not found] ` <52091E6B.10800-3s7WtUTddSA@public.gmane.org>
2013-08-13 3:22 ` Rich Felker
2013-08-13 3:22 ` Rich Felker
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=20130806155415.GA12926@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=dalias-/miJ2pyFWUyWIDz0JBNUog@public.gmane.org \
--cc=joseph-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org \
--cc=libc-alpha-9JcytcrH/bA+uJoB2kUjGw@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@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 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.