[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240212105237.674e6fcb@canb.auug.org.au>
Date: Mon, 12 Feb 2024 10:52:37 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Christian Brauner <brauner@...nel.org>
Cc: Kent Overstreet <kent.overstreet@...ux.dev>, 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 include/linux/highmem.h:5,
from include/linux/bvec.h:10,
from include/linux/blk_types.h:10,
from include/linux/blkdev.h:9,
from fs/btrfs/super.c:6:
include/linux/fs.h: In function 'super_set_sysfs_name_generic':
include/linux/fs.h:2597:9: error: function 'super_set_sysfs_name_generic' might be a candidate for 'gnu_printf' format attribute [-Werror=suggest-attribute=format]
2597 | vsnprintf(sb->s_sysfs_name, sizeof(sb->s_sysfs_name), fmt, args);
| ^~~~~~~~~
cc1: all warnings being treated as errors
and many more similar.
Caused by commit
eeea5d25d4a7 ("fs: add FS_IOC_GETFSSYSFSPATH")
This new finction is not used anywhere, so just remove it for now?
I have used the vfs-brauner tree from next-20240209 for today.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists