This is the mail archive of the
mailing list for the glibc project.
Re: O_EXEC and O_SEARCH
- From: KOSAKI Motohiro <kosaki dot motohiro at gmail dot com>
- To: Rich Felker <dalias at aerifal dot cx>
- Cc: libc-alpha <libc-alpha at sourceware dot org>, musl at lists dot openwall dot com
- Date: Fri, 22 Feb 2013 22:05:03 -0500
- Subject: Re: O_EXEC and O_SEARCH
- References: <20130222004540.GA8836@brightrain.aerifal.cx>
> I'd like to have a conversation with the glibc team about O_EXEC and
> O_SEARCH in the interest of hopefully developing a unified plan for
> supporting them on Linux. Presumably the reason glibc still does not
> have them is that Linux O_PATH does not exactly match their semantics
> in some cases, and O_PATH is sufficiently broken on many kernel
> versions to make offering it problematic. In particular, current
> coreutils break badly on most kernel versions around 2.6.39-3.6 or so
> if O_SEARCH and O_EXEC are defined as O_PATH.
I'm curious why don't you implement them in kernel directly?