[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<174915723301.3244853.343931856692302765.git-patchwork-notify@kernel.org>
Date: Thu, 05 Jun 2025 21:00:33 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Blake Jones <blakejones@...gle.com>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
martin.lau@...ux.dev, eddyz87@...il.com, song@...nel.org,
yonghong.song@...ux.dev, john.fastabend@...il.com, kpsingh@...nel.org,
sdf@...ichev.me, haoluo@...gle.com, jolsa@...nel.org, mykolal@...com,
shuah@...nel.org, ihor.solodrai@...ux.dev, namhyung@...nel.org,
irogers@...gle.com, bpf@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org
Subject: Re: [PATCH v3 1/2] libbpf: add support for printing BTF character
arrays
as strings
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:
On Tue, 3 Jun 2025 13:37:00 -0700 you wrote:
> The BTF dumper code currently displays arrays of characters as just that -
> arrays, with each character formatted individually. Sometimes this is what
> makes sense, but it's nice to be able to treat that array as a string.
>
> This change adds a special case to the btf_dump functionality to allow
> 0-terminated arrays of single-byte integer values to be printed as
> character strings. Characters for which isprint() returns false are
> printed as hex-escaped values. This is enabled when the new ".emit_strings"
> is set to 1 in the btf_dump_type_data_opts structure.
>
> [...]
Here is the summary with links:
- [v3,1/2] libbpf: add support for printing BTF character arrays as strings
https://git.kernel.org/bpf/bpf-next/c/87c9c79a02b4
- [v3,2/2] Tests for the ".emit_strings" functionality in the BTF dumper.
https://git.kernel.org/bpf/bpf-next/c/a570f386f3d1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists