From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Thomas Gleixner <tglx@linutronix•de>,
Ingo Molnar <mingo@redhat•com>, "H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>
Cc: Ingo Molnar <mingo@kernel•org>,
Josh Poimboeuf <jpoimboe@kernel•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the tip-fixes tree
Date: Wed, 26 Mar 2025 10:38:54 +1100 [thread overview]
Message-ID: <20250326103854.309e3c60@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
Hi all,
After merging the tip-fixes tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from builtin-check.c:16:
In function 'save_argv',
inlined from 'objtool_run' at builtin-check.c:296:2:
tools/objtool/include/objtool/warn.h:47:17: error: '%s' directive argument is null [-Werror=format-overflow=]
47 | "%s%s%s: objtool: " format "\n", \
| ^~~~~~~~~~~~~~~~~~~
tools/objtool/include/objtool/warn.h:92:9: note: in expansion of macro 'WARN'
92 | WARN("%s: " format " failed: %s", __func__, ##__VA_ARGS__, strerror(errno))
| ^~~~
builtin-check.c:241:25: note: in expansion of macro 'WARN_GLIBC'
241 | WARN_GLIBC("strdup(%s)", orig_argv[i]);
| ^~~~~~~~~~
cc1: all warnings being treated as errors
Caused (or exposed?) by commit
c5995abe1547 ("objtool: Improve error handling")
I have used the tip-fixes tree from next-20250325 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-03-25 23:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 23:38 Stephen Rothwell [this message]
2025-03-26 1:12 ` linux-next: build failure after merge of the tip-fixes tree Josh Poimboeuf
-- strict thread matches above, loose matches on Subject: below --
2026-04-08 12:44 Mark Brown
2026-04-08 14:50 ` Mark Brown
2026-04-08 14:54 ` Thomas Weißschuh
2026-04-08 15:21 ` Thomas Gleixner
2026-04-08 15:45 ` Mark Brown
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=20250326103854.309e3c60@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=hpa@zytor$(echo .)com \
--cc=jpoimboe@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@kernel$(echo .)org \
--cc=mingo@redhat$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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