Re: [PATCH v6 1/4] openat2: new OPENAT2_REGULAR flag support

Jori Koolstra <[email protected]> Thu, 16 Apr 2026 23:36:31 +0200 (CEST)

Newsgroups	dev.linux.lists.gfs2,dev.linux.lists.v9fs,org.kernel.vger.ceph-devel,org.kernel.vger.linux-api,org.kernel.vger.linux-cifs,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-kselftest,org.kernel.vger.linux-nfs
Message-ID	<[email protected]>

> Op 16-04-2026 17:15 CEST schreef Christian Brauner <[email protected]>:
> 
>  
> On Thu, Apr 16, 2026 at 05:03:26PM +0200, Jori Koolstra wrote:
> > 
> > If I recall correctly, Aleksa has suggested we might also want to add
> > O_EMPTYPATH to openat() instead of only allowing this for openat2().
> > I am waiting to see what Christian thinks of this.
> 
> We can do that, yes. For O_EMPTYPATH that is workable.

All right, then I'll update the patch this weekend.

> 
> I don't mind too much if we leave OPENAT2_REGUALR in the 32-bit flag
> space. It'll silently be ignored but the flag name should give it away.

I would also prefer to have the bits separated. Although it is unlikely
that we will add so many O_* that we will ever run out of space, it just
seems cleaner, and at no cost. But it's not too important.

Thanks,
Jori.