From: ebiederm@xmission.com (Eric W. Biederman)
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Yu Zhao <yuzhao@google.com>, Alexey Gladkov <legion@kernel.org>
Subject: Re: linux-next: build failure after merge of the userns tree
Date: Wed, 20 Oct 2021 11:00:14 -0500 [thread overview]
Message-ID: <875ytrptyp.fsf@disp2133> (raw)
In-Reply-To: <20211020144651.10321529@canb.auug.org.au> (Stephen Rothwell's message of "Wed, 20 Oct 2021 14:46:51 +1100")
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> After merging the userns tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from arch/x86/include/asm/bug.h:84,
> from include/linux/bug.h:5,
> from arch/x86/include/asm/paravirt.h:15,
> from arch/x86/include/asm/irqflags.h:63,
> from include/linux/irqflags.h:16,
> from include/linux/rcupdate.h:26,
> from include/linux/rculist.h:11,
> from include/linux/pid.h:5,
> from include/linux/sched.h:14,
> from security/keys/process_keys.c:9:
> security/keys/process_keys.c: In function 'key_change_session_keyring':
> security/keys/process_keys.c:923:16: error: format '%s' expects a matching 'char *' argument [-Werror=format=]
> 923 | WARN_ONCE(1, "In %s get_ucounts failed\n");
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
> include/asm-generic/bug.h:99:17: note: in definition of macro '__WARN_printf'
> 99 | __warn_printk(arg); \
> | ^~~
> include/linux/once_lite.h:19:4: note: in expansion of macro 'WARN'
> 19 | func(__VA_ARGS__); \
> | ^~~~
> include/asm-generic/bug.h:150:2: note: in expansion of macro 'DO_ONCE_LITE_IF'
> 150 | DO_ONCE_LITE_IF(condition, WARN, 1, format)
> | ^~~~~~~~~~~~~~~
> security/keys/process_keys.c:923:3: note: in expansion of macro 'WARN_ONCE'
> 923 | WARN_ONCE(1, "In %s get_ucounts failed\n");
> | ^~~~~~~~~
> security/keys/process_keys.c:923:21: note: format string is defined here
> 923 | WARN_ONCE(1, "In %s get_ucounts failed\n");
> | ~^
> | |
> | char *
> cc1: all warnings being treated as errors
>
> Caused by commit
>
> 346b5b4aa656 ("ucounts: Move get_ucounts from cred_alloc_blank to key_change_session_keyring")
>
> I have used the userns tree from next-20211019 for today.
Thank you very much for catching that.
I am now quite embarrassed I did not catch that myself.
Eric
next prev parent reply other threads:[~2021-10-20 16:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 3:46 linux-next: build failure after merge of the userns tree Stephen Rothwell
2021-10-20 16:00 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-16 5:56 Stephen Rothwell
2022-03-16 13:54 ` Eric W. Biederman
2021-12-17 7:34 Stephen Rothwell
2021-12-17 16:53 ` Eric W. Biederman
2021-12-17 7:13 Stephen Rothwell
2021-10-07 3:47 Stephen Rothwell
2021-10-07 18:56 ` Eric W. Biederman
2020-05-21 8:22 Stephen Rothwell
2018-03-28 7:41 Stephen Rothwell
2018-03-28 18:32 ` Eric W. Biederman
2018-01-26 1:05 Stephen Rothwell
2018-01-26 2:45 ` Eric W. Biederman
2017-07-20 3:25 Stephen Rothwell
2017-07-20 12:17 ` Eric W. Biederman
2015-05-25 10:39 Stephen Rothwell
2014-04-17 5:12 Stephen Rothwell
2014-04-17 7:18 ` Eric W. Biederman
2014-04-22 1:34 ` Stephen Rothwell
2013-11-08 7:07 Stephen Rothwell
2013-11-08 23:15 ` Eric W. Biederman
2013-11-11 5:25 ` Stephen Rothwell
2013-11-08 6:58 Stephen Rothwell
2013-11-08 7:27 ` Christoph Hellwig
2013-11-08 15:55 ` Al Viro
2013-11-08 22:50 ` Eric W. Biederman
2013-11-09 8:32 ` Christoph Hellwig
2012-09-24 12:18 Stephen Rothwell
2012-05-21 7:50 Stephen Rothwell
2012-05-21 22:05 ` Eric W. Biederman
2012-05-14 9:13 Stephen Rothwell
2012-05-16 1:12 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875ytrptyp.fsf@disp2133 \
--to=ebiederm@xmission.com \
--cc=legion@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=yuzhao@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).