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

[Dorjoy Chowdhury]

Hi Mark,

On Mon, May 18, 2026 at 10:32 PM Mark Brown <broonie@xxxxxxxxxx> wrote:
>
> On Mon, May 18, 2026 at 11:47:24AM +0100, Mark Brown wrote:
> > Hi all,
> >
> > After merging the vfs-brauner tree, today's linux-next build (arm64
> > allnoconfig) failed like this:
>
> > Caused by commits
>
> >   3adfed795a99d (openat2: new OPENAT2_REGULAR flag support)
> >   6703991ad3a35 (vfs: add O_EMPTYPATH to openat(2)/openat2(2))
>
> > interacting with each other.  Due to complex conflcits with netfs on the
> > old vfs-brauner tree I have applied the following fixup but since both
> > commits are coming from the vfs-brauner tree it's really not a merge
> > fixup:
>
> ...and my fixup fails to build on sparc64_defconfig :/

(1 << 26) doesn't seem to be  0100000000 rather 0400000000 .
0100000000 conflicts with O_PATH in
arch/sparc/include/uapi/asm/fcntl.h

dorjoy@desktop:~$ python3
Python 3.14.4 (main, Apr 16 2026, 00:00:00) [GCC 16.0.1 20260321 (Red
Hat 16.0.1-0)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> a = (1 << 26)
>>> oct(a)
'0o400000000'

I looked at the O_EMPTYPATH changes in git.kernel.org and it defines
O_EMPTYPATH only in include/uapi/asm-generic/fcntl.h . That is why it
was probably chosen to be (1 << 26) i.e., 0400000000  since at that
time this value did not conflict with the other explicit values in
architecture specific fcnl.h files. But as far as I see, I defined
0400000000 as OPENAT2_REGULAR in arch/sparc/include/uapi/asm/fcntl.h
during my work. So this value probably needs to be something else, for
example, (1 << 27) i.e., 01000000000 to avoid conflict after merging?

Regards,
Dorjoy