[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20251208141618.2805983-1-andriy.shevchenko@linux.intel.com>
Date: Mon, 8 Dec 2025 15:16:18 +0100
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Peter Zijlstra <peterz@...radead.org>,
linux-kernel@...r.kernel.org
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: [PATCH v1 1/1] bug: Mark __warn_printf() with __printf() attribute
__warn_printf() is using printf() type of format, and compiler
is not happy about them as is:
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);
| ^~~~~~~
Fix the compilation errors by adding __printf() attribute.
Fixes: 5c47b7f3d1a9 ("bug: Add BUG_FORMAT_ARGS infrastructure")
Signed-off-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
---
lib/bug.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/bug.c b/lib/bug.c
index edd9041f89f3..d7db57280ab7 100644
--- a/lib/bug.c
+++ b/lib/bug.c
@@ -173,7 +173,7 @@ struct bug_entry *find_bug(unsigned long bugaddr)
return module_find_bug(bugaddr);
}
-static void __warn_printf(const char *fmt, struct pt_regs *regs)
+static __printf(1, 0) void __warn_printf(const char *fmt, struct pt_regs *regs)
{
if (!fmt)
return;
--
2.50.1
Powered by blists - more mailing lists