Re: linux-next: build failure after merge of the vfs-brauner tree

[Christian Brauner]

On Wed, Feb 04, 2026 at 02:31:06PM +0000, Mark Brown wrote:
> On Mon, Feb 02, 2026 at 02:58:35PM +0000, Mark Brown wrote:
> > On Tue, Jan 27, 2026 at 11:45:44AM +0000, Mark Brown wrote:
> > > Hi all,
> > > 
> > > After merging the vfs-brauner tree, today's linux-next build
> > > (arm64 kselftest) failed like this:
> > 
> > This issue is still present in today's -next.
> 
> This means that vfs-brauner is still held at the version from
> next-20260126 and none of the below commits have been in -next:

This should've been fixed. Not sure what happened.
I've reassembled vfs.all completely just to be sure.

> 
> Amir Goldstein (4):
>       fs: add helpers name_is_dot{,dot,_dotdot}
>       ovl: use name_is_dot* helpers in readdir code
>       exportfs: clarify the documentation of open()/permission() expotrfs ops
>       nfsd: do not allow exporting of special kernel filesystems
> 
> Andrey Albershteyn (3):
>       fs: reset read-only fsflags together with xflags
>       fs: add FS_XFLAG_VERITY for fs-verity files
>       fsverity: add tracepoints
> 
> Chelsy Ratnawat (1):
>       fs: dcache: fix typo in enum d_walk_ret comment
> 
> Christian Brauner (6):
>       mount: start iterating from start of rbtree
>       mount: simplify __do_loopback()
>       mount: add FSMOUNT_NAMESPACE
>       tools: update mount.h header
>       selftests/statmount: add statmount_alloc() helper
>       selftests: add FSMOUNT_NAMESPACE tests
> 
> Joanne Koong (1):
>       iomap: fix invalid folio access after folio_end_read()
> 
> Qiliang Yuan (1):
>       fs/file: optimize close_range() complexity from O(N) to O(Sparse)
> 
> Qing Wang (1):
>       ovl: Fix uninit-value in ovl_fill_real
> 
> Tamir Duberstein (1):
>       rust: seq_file: replace `kernel::c_str!` with C-Strings
>