Re: Request for comments: reserving a value for O_SEARCH and O_EXEC

On Tue, 6 Aug 2013, Rich Felker wrote:

Of course, the userspace fallback code could detect such failures and
retry with O_RDONLY, so maybe it's not such a big issue. With a
working O_PATH, open should never fail with EISDIR or EACCES, so these
errors could be used as a condition to retry.

Surely you'll still get EACCES when some component in the specified path, 
not the last one, lacks search permission?

-- 
Joseph S. Myers
joseph-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org