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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240726100041.142b6e35@canb.auug.org.au>
Date: Fri, 26 Jul 2024 10:00:41 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Christian Brauner <brauner@...nel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: build failure after merge of the vfs-brauner tree

Hi all,

After merging the vfs-brauner tree, today's linux-next build (x86_64
allmodconfig) failed like this:

In file included from fs/smb/server/unicode.c:14:
fs/smb/server/smb_common.h:46: error: "F_CREATED" redefined [-Werror]
   46 | #define F_CREATED       2
      | 
In file included from include/linux/fcntl.h:6,
                 from include/linux/fs.h:26,
                 from fs/smb/server/unicode.c:9:
include/uapi/linux/fcntl.h:20: note: this is the location of the previous definition
   20 | #define F_CREATED       (F_LINUX_SPECIFIC_BASE + 4)
      | 
cc1: all warnings being treated as errors

Caused by commit

  a621ce4eed14 ("fcntl: add F_CREATED")

Is that commit really intended for this merge window?

I have used the vfs-brauner tree from next-20240725 for today.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped