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 23:54:17 -0500
- Subject: Re: O_EXEC and O_SEARCH
- References: <20130222004540.GA8836@brightrain.aerifal.cx>
> Right now, we're offering O_EXEC and O_SEARCH in musl libc, defining
> them as O_PATH. As long as recent Linux is used, this gives nearly
> correct semantics, except that combined with O_NOFOLLOW they do not
> fail when the final component is a symbolic link. I believe it's
> possible to work around this issue on sufficiently modern kernels
> where fstat works on O_PATH file descriptors, but adding the
> workaround whenever O_PATH|O_NOFOLLOW is in the flags would change the
> semantics when O_PATH is used by the caller rather than O_EXEC or
> O_SEARCH, since the value is equal. I'm not sure this is desirable.
I have one more question. If I understand correctly, O_NOFOLLOW is
POSIX. Why do you think the current behavior is not correct?
And, as far as I observed, current linux man pages don't tell us
behavior. Is this really intentional result? How do you confirmed?
I mean the current behavior is not natural to me and I doubt it is not