The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>, linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v1 1/1] bug: Mark __warn_printf() with __printf() attribute
Date: Wed, 4 Feb 2026 17:59:37 +0200	[thread overview]
Message-ID: <aYNs6fQLfvLah_iB@smile.fi.intel.com> (raw)
In-Reply-To: <20251208141618.2805983-1-andriy.shevchenko@linux.intel.com>

+Cc: Arnd (just FYI)

On Mon, Dec 08, 2025 at 03:16:18PM +0100, Andy Shevchenko wrote:
> __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@linux.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;

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2026-02-04 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08 14:16 [PATCH v1 1/1] bug: Mark __warn_printf() with __printf() attribute Andy Shevchenko
2025-12-16  9:35 ` Brendan Jackman
2026-02-04 15:59 ` Andy Shevchenko [this message]
2026-02-04 16:20   ` Arnd Bergmann

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=aYNs6fQLfvLah_iB@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --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