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

[Mark Brown]

On Mon, May 18, 2026 at 11:06:05PM +0600, Dorjoy Chowdhury wrote:
> On Mon, May 18, 2026 at 10:32 PM Mark Brown <broonie@xxxxxxxxxx> wrote:

> > >   3adfed795a99d (openat2: new OPENAT2_REGULAR flag support)
> > >   6703991ad3a35 (vfs: add O_EMPTYPATH to openat(2)/openat2(2))

> > ...and my fixup fails to build on sparc64_defconfig :/

> (1 << 26) doesn't seem to be  0100000000 rather 0400000000 .

Yeah, like I said I renumbered due to the conflict with the asm-generic
OPENAT2_REGULAR.

> 0100000000 conflicts with O_PATH in
> arch/sparc/include/uapi/asm/fcntl.h

Figured it'd be an arch specific version of a similar thing - I didn't
audit them as you can see.

> 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?

Yeah, just some value that isn't already in use - the compile assert is
doing it's job here.

Attachment: signature.asc
Description: PGP signature