From: Quentin Monnet <qmo@kernel.org>
To: Hungyu Lin <dennylin0707@gmail.com>, ast@kernel.org, bpf@vger.kernel.org
Cc: andrii@kernel.org, daniel@iogearbox.net, yonghong.song@linux.dev,
eddyz87@gmail.com, ihor.solodrai@linux.dev, shuah@kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 3/3] selftests/bpf: Cover enum signedness and legacy name matching
Date: Mon, 2 Nov 2026 16:28:23 +0100 [thread overview]
Message-ID: <0d7672ae-a856-4f0e-9aa8-52e897bcd4da@kernel.org> (raw)
In-Reply-To: <20261101103221.51534-4-dennylin0707@gmail.com>
On 01/11/2026 11:32, Hungyu Lin wrote:
> Exercise unsigned enum values with their high bit set and signed
> controls through libbpf's data dumper. Include ordinary enums stored in
> eight bytes and legacy BTF with kflag clear so normalization does not
> lose existing names or match only the low 32 bits of wider data.
>
> Extend bpftool_map_dump with BTF-backed array maps and check both JSON
> and plain output. Cover narrow unsigned names, signed and unsigned
> numeric fallbacks, legacy enum names, both enumerator orders for
> ambiguous narrow names, and unmatched ENUM64 values.
>
> Build legacy enum records through the public BTF API and load them into
> the kernel before invoking bpftool. Initialize map data at its actual
> width so the tests also work on big-endian hosts.
>
> Suggested-by: Alexei Starovoitov <ast@kernel.org>
> Signed-off-by: Hungyu Lin <dennylin0707@gmail.com>
Acked-by: Quentin Monnet <qmo@kernel.org>
prev parent reply other threads:[~2026-11-02 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 10:32 [PATCH bpf-next v3 0/3] Normalize enum values in libbpf and bpftool Hungyu Lin
2026-11-01 10:32 ` [PATCH bpf-next v3 1/3] libbpf: Normalize enum values according to signedness Hungyu Lin
2026-11-01 10:32 ` [PATCH bpf-next v3 2/3] bpftool: Preserve unsigned enum values in data dumps Hungyu Lin
2026-11-02 15:28 ` Quentin Monnet
2026-11-01 10:32 ` [PATCH bpf-next v3 3/3] selftests/bpf: Cover enum signedness and legacy name matching Hungyu Lin
2026-11-02 15:28 ` Quentin Monnet [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=0d7672ae-a856-4f0e-9aa8-52e897bcd4da@kernel.org \
--to=qmo@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dennylin0707@gmail.com \
--cc=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=yonghong.song@linux.dev \
/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