Re: [RFC PATCH v2 1/3] vfs: add support for empty path to openat2(2)

[Aleksa Sarai]

On 2026-03-30, Jeff Layton <jlayton@xxxxxxxxxx> wrote:
> Looks sane to me. Can this be merged apart from the rest of the series?
> It doesn't seem like the transitive stuff is dependent on this.

No it isn't. I mentioned this in another mail but my thinking from a
long time ago was that we should harden these re-open paths if we want
to fully support O_EMPTYPATH -- but we already allow all of this stuff
today so we might as well merge this thing and make everyone's lives
easier. The transitive stuff also needs a lot more work IMHO, and I
suspect the full version is going to be a hard sell.

My only comment is that I would like this to be usable in open() as it
is one of the very few cases of an O_* flag that is actually backwards
compatible with all of the brokenness of open() and the systemd folks
would probably want to use it (they can't use openat2() yet).

-- 
Aleksa Sarai
https://www.cyphar.com/

Attachment: signature.asc
Description: PGP signature