From: Brendan Jackman <jackmanb@google.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, kees@kernel.org,
acarmina@redhat.com, jpoimboe@kernel.org, mark.rutland@arm.com,
maciej.wieczor-retman@intel.com,
Brendan Jackman <jackmanb@google.com>
Subject: [PATCH] bug: hush suggest-attribute=format for __warn_printf()
Date: Sun, 07 Dec 2025 03:53:18 +0000 [thread overview]
Message-ID: <20251207-warn-printf-gcc-v1-1-b597d612b94b@google.com> (raw)
Recent additions to this function cause GCC 14.3.0 to get excited and
suggest a missing attribute:
lib/bug.c: In function ‘__warn_printf’:
lib/bug.c:187:25: error: function ‘__warn_printf’ might be a candidate for ‘gnu_printf’ format attribute [-Werror=suggest-attribute=format]
187 | vprintk(fmt, *args);
| ^~~~~~~
Disable the diagnostic locally, following the pattern used for stuff
like va_format().
Fixes: 5c47b7f3d1a9 ("bug: Add BUG_FORMAT_ARGS infrastructure")
Signed-off-by: Brendan Jackman <jackmanb@google.com>
---
lib/bug.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/lib/bug.c b/lib/bug.c
index edd9041f89f3aa613af71e4f107b52a4f4dc71f4..051891f874439d66f907e043cf52b954b3ea564b 100644
--- a/lib/bug.c
+++ b/lib/bug.c
@@ -173,6 +173,9 @@ struct bug_entry *find_bug(unsigned long bugaddr)
return module_find_bug(bugaddr);
}
+__diag_push();
+__diag_ignore(GCC, all, "-Wsuggest-attribute=format",
+ "Not a valid __printf() conversion candidate.");
static void __warn_printf(const char *fmt, struct pt_regs *regs)
{
if (!fmt)
@@ -192,6 +195,7 @@ static void __warn_printf(const char *fmt, struct pt_regs *regs)
printk("%s", fmt);
}
+__diag_pop();
static enum bug_trap_type __report_bug(struct bug_entry *bug, unsigned long bugaddr, struct pt_regs *regs)
{
---
base-commit: 5e8f8a25efb277ac6f61f553f0c533ff1402bd7c
change-id: 20251207-warn-printf-gcc-8da08c251c1c
Best regards,
--
Brendan Jackman <jackmanb@google.com>
next reply other threads:[~2025-12-07 3:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-07 3:53 Brendan Jackman [this message]
2025-12-08 8:38 ` [PATCH] bug: hush suggest-attribute=format for __warn_printf() Peter Zijlstra
2025-12-08 8:50 ` Brendan Jackman
2025-12-08 8:58 ` Peter Zijlstra
2025-12-09 9:16 ` [tip: core/urgent] bug: Hush " tip-bot2 for Brendan Jackman
2025-12-12 9:10 ` tip-bot2 for Brendan Jackman
2025-12-12 9:29 ` tip-bot2 for Brendan Jackman
2025-12-16 4:24 ` [PATCH] bug: hush " Andrew Morton
2025-12-16 8:49 ` Peter Zijlstra
2025-12-16 9:16 ` Brendan Jackman
2025-12-16 12:36 ` David Laight
2025-12-16 12:43 ` Brendan Jackman
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=20251207-warn-printf-gcc-v1-1-b597d612b94b@google.com \
--to=jackmanb@google.com \
--cc=acarmina@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jpoimboe@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=mark.rutland@arm.com \
--cc=peterz@infradead.org \
/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