All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Arnd Bergmann <arnd@kernel.org>
Cc: kees@kernel.org, pmladek@suse.com,
	andriy.shevchenko@linux.intel.com, arnd@arndb.de, lkp@intel.com,
	alexei.starovoitov@gmail.com, andy@kernel.org, ast@kernel.org,
	brgl@kernel.org, linux-kernel@vger.kernel.org,
	linux-hardening@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH] vsnprintf: drop __printf() attributes on binary printing functions
Date: Thu, 12 Feb 2026 01:28:33 +0000	[thread overview]
Message-ID: <177085971357.817736.11815620280391831698.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260204132643.1302967-1-arnd@kernel.org>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Petr Mladek <pmladek@suse.com>:

On Wed,  4 Feb 2026 14:26:23 +0100 you wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> The printf() format attributes are applied inconsistently for the binary
> printf helpers, which causes warnings for the bpf_trace code using
> them from functions that pass down format strings:
> 
>     kernel/trace/bpf_trace.c: In function '____bpf_trace_printk':
>     kernel/trace/bpf_trace.c:377:9: error: function '____bpf_trace_printk' might be a candidate for 'gnu_printf' format attribute [-Werror=suggest-attribute=format]
>       377 |         ret = bstr_printf(data.buf, MAX_BPRINTF_BUF, fmt, data.bin_args);
>           |         ^~~
> 
> [...]

Here is the summary with links:
  - vsnprintf: drop __printf() attributes on binary printing functions
    https://git.kernel.org/bpf/bpf-next/c/b07829d546c8

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-02-12  1:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-04 13:26 [PATCH] vsnprintf: drop __printf() attributes on binary printing functions Arnd Bergmann
2026-02-04 13:47 ` Andy Shevchenko
2026-02-05  8:53 ` Petr Mladek
2026-02-05 10:12   ` Arnd Bergmann
2026-02-05 15:58     ` Alexei Starovoitov
2026-02-06  9:28       ` Petr Mladek
2026-02-12  1:28 ` patchwork-bot+netdevbpf [this message]

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=177085971357.817736.11815620280391831698.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy@kernel.org \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brgl@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=pmladek@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.