From: patchwork-bot+netdevbpf@kernel.org
To: Hungyu Lin <dennylin0707@gmail.com>
Cc: qmo@kernel.org, bpf@vger.kernel.org, andrii.nakryiko@gmail.com,
ast@kernel.org, daniel@iogearbox.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2] bpftool: avoid sign extension in unsigned enum JSON dumps
Date: Fri, 30 Oct 2026 22:40:06 +0000 [thread overview]
Message-ID: <179340000629.1810026.13611068664375441982.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261030195343.79712-1-dennylin0707@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 30 Oct 2026 19:53:43 +0000 you wrote:
> The BTF enum value is stored in a signed 32-bit field even when the
> enum is unsigned. Passing it directly to jsonw_uint_field(), which
> takes a uint64_t, sign-extends values with bit 31 set. For example,
> 0xffffffffU is printed as 18446744073709551615 instead of 4294967295
> by bpftool -j btf dump.
>
> Cast the value to __u32 before widening it, matching the conversion
> already used for plain-text output.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpftool: avoid sign extension in unsigned enum JSON dumps
https://git.kernel.org/bpf/bpf-next/c/eaae576c34d7
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-10-30 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 19:53 [PATCH bpf-next v2] bpftool: avoid sign extension in unsigned enum JSON dumps Hungyu Lin
2026-10-30 22:40 ` 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=179340000629.1810026.13611068664375441982.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dennylin0707@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qmo@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