Re: [PATCH v6 0/4] OPENAT2_REGULAR flag support for openat2

[Christian Brauner]

On Thu, Apr 16, 2026 at 09:22:03PM +0600, Dorjoy Chowdhury wrote:
> On Thu, Apr 16, 2026 at 7:07 PM Christian Brauner <brauner@xxxxxxxxxx> wrote:
> >
> > On Sat, 28 Mar 2026 23:22:21 +0600, Dorjoy Chowdhury wrote:
> > > I came upon this "Ability to only open regular files" uapi feature suggestion
> > > from https://uapi-group.org/kernel-features/#ability-to-only-open-regular-files
> > > and thought it would be something I could do as a first patch and get to
> > > know the kernel code a bit better.
> > >
> > > The following filesystems have been tested by building and booting the kernel
> > > x86 bzImage in a Fedora 43 VM in QEMU. I have tested with OPENAT2_REGULAR that
> > > regular files can be successfully opened and non-regular files (directory, fifo etc)
> > > return -EFTYPE.
> > > - btrfs
> > > - NFS (loopback)
> > > - SMB (loopback)
> > >
> > > [...]
> >
> > - I've added an explanation why OPENAT2_REGULAR is only needed for some
> >   ->atomic_open() implementers but not others. What I don't like is that
> >   we need all that custom handling in there but it's managable.
> >
> > - I dropped the topmost style conversions. They really don't belong
> >   there and if we switch to something better we should use (1 << <nr>).
> >
> > - I split the EFTYPE errno introduction into a separate patch.
> >
> > ---
> 
> Thanks for fixing up and picking this one up!
> 
> >
> > Applied to the vfs-7.2.openat.regular branch of the vfs/vfs.git tree.
> > Patches in the vfs-7.2.openat.regular branch should appear in linux-next soon.
> >
> 
> I don't see a vfs-7.2.openat.regular branch in vfs/vfs.git tree in
> git.kernel.org.  Maybe this hasn't been pushed yet?

Nothing will get pushed prior to -rc1 which is due this Sunday.