From: patchwork-bot+netdevbpf@kernel.org
To: Yihan Ding <dingyihan@uniontech.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, shuah@kernel.org, alan.maguire@oracle.com,
paul.chaignon@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf v3 0/2] bpf: allow UTF-8 literals in bpf_bprintf_prepare()
Date: Thu, 16 Apr 2026 23:00:08 +0000 [thread overview]
Message-ID: <177638040855.3431809.14537321276770181909.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260416120142.1420646-1-dingyihan@uniontech.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 16 Apr 2026 20:01:40 +0800 you wrote:
> bpf_bprintf_prepare() currently rejects any non-ASCII byte in format
> strings, so helpers such as bpf_trace_printk() fail to emit UTF-8
> literal text even when those bytes are not part of a format specifier.
>
> Keep plain text permissive while continuing to parse '%' sequences as
> ASCII-only. Patch 1 updates snprintf_negative() at the same time so the
> selftests stay consistent during bisection. Patch 2 then extends
> trace_printk coverage for both the valid UTF-8 literal case and the
> invalid non-ASCII-after-'%' case.
>
> [...]
Here is the summary with links:
- [bpf,v3,1/2] bpf: allow UTF-8 literals in bpf_bprintf_prepare()
https://git.kernel.org/bpf/bpf/c/b960430ea886
- [bpf,v3,2/2] selftests/bpf: cover UTF-8 trace_printk output
https://git.kernel.org/bpf/bpf/c/4198ff31edb1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-04-16 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 12:01 [PATCH bpf v3 0/2] bpf: allow UTF-8 literals in bpf_bprintf_prepare() Yihan Ding
2026-04-16 12:01 ` [PATCH bpf v3 1/2] " Yihan Ding
2026-04-16 13:03 ` sashiko-bot
2026-04-16 22:32 ` Paul Chaignon
2026-04-16 12:01 ` [PATCH bpf v3 2/2] selftests/bpf: cover UTF-8 trace_printk output Yihan Ding
2026-04-16 22:35 ` Paul Chaignon
2026-04-16 23:00 ` 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=177638040855.3431809.14537321276770181909.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dingyihan@uniontech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.chaignon@gmail.com \
--cc=shuah@kernel.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