From: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>,
Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>,
bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
kafai@meta.com, kernel-team@meta.com
Cc: Mykyta Yatsenko <yatsenko@meta.com>
Subject: Re: [PATCH bpf-next] bpftool: Fix handling enum64 in btf dump sorting
Date: Mon, 2 Sep 2024 17:52:59 +0100 [thread overview]
Message-ID: <83f3b5c9-ec98-4a70-ace2-1e40187704b3@gmail.com> (raw)
In-Reply-To: <695c2a92-a79d-5f8d-e3a9-00cd11b5f961@iogearbox.net>
On 02/09/2024 17:22, Daniel Borkmann wrote:
> On 9/1/24 11:30 PM, "Mykyta Yatsenko mykyta.yatsenko5"@gmail.com wrote:
>> From: Mykyta Yatsenko <yatsenko@meta.com>
>>
>> Wrong function is used to access the first enum64 element.
>> Substituting btf_enum(t) with btf_enum64(t) for BTF_KIND_ENUM64.
>>
>> Signed-off-by: Mykyta Yatsenko <yatsenko@meta.com>
>> ---
>> tools/bpf/bpftool/btf.c | 13 ++++++++++---
>> 1 file changed, 10 insertions(+), 3 deletions(-)
>>
>> diff --git a/tools/bpf/bpftool/btf.c b/tools/bpf/bpftool/btf.c
>> index 6789c7a4d5ca..b0f12c511bb3 100644
>> --- a/tools/bpf/bpftool/btf.c
>> +++ b/tools/bpf/bpftool/btf.c
>> @@ -557,16 +557,23 @@ static const char *btf_type_sort_name(const
>> struct btf *btf, __u32 index, bool f
>> const struct btf_type *t = btf__type_by_id(btf, index);
>> switch (btf_kind(t)) {
>> - case BTF_KIND_ENUM:
>> - case BTF_KIND_ENUM64: {
>> + case BTF_KIND_ENUM: {
>> int name_off = t->name_off;
>> /* Use name of the first element for anonymous enums if
>> allowed */
>> - if (!from_ref && !t->name_off && btf_vlen(t))
>> + if (!from_ref && !name_off && btf_vlen(t))
>> name_off = btf_enum(t)->name_off;
>> return btf__name_by_offset(btf, name_off);
>> }
>
> Small nit, could we consolidate the logic into the below? Still
> somewhat nicer
> than duplicating all of the rest.
Thanks for the suggestion, this makes sense, I will apply it.
>
> diff --git a/tools/bpf/bpftool/btf.c b/tools/bpf/bpftool/btf.c
> index 6789c7a4d5ca..aae6f5262c6a 100644
> --- a/tools/bpf/bpftool/btf.c
> +++ b/tools/bpf/bpftool/btf.c
> @@ -562,8 +562,10 @@ static const char *btf_type_sort_name(const
> struct btf *btf, __u32 index, bool f
> int name_off = t->name_off;
>
> /* Use name of the first element for anonymous enums
> if allowed */
> - if (!from_ref && !t->name_off && btf_vlen(t))
> - name_off = btf_enum(t)->name_off;
> + if (!from_ref && !name_off && btf_vlen(t))
> + name_off = btf_kind(t) == BTF_KIND_ENUM64 ?
> + btf_enum64(t)->name_off :
> + btf_enum(t)->name_off;
>
> return btf__name_by_offset(btf, name_off);
> }
>
> Thanks,
> Daniel
>
next prev parent reply other threads:[~2024-09-02 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 21:30 [PATCH bpf-next] bpftool: Fix handling enum64 in btf dump sorting Mykyta
2024-09-02 16:22 ` Daniel Borkmann
2024-09-02 16:52 ` Mykyta Yatsenko [this message]
2024-09-03 16:51 ` Andrii Nakryiko
2024-09-03 18:27 ` Daniel Borkmann
-- strict thread matches above, loose matches on Subject: below --
2024-09-02 17:17 Mykyta Yatsenko
2024-09-02 18:52 ` Quentin Monnet
2024-09-02 20:50 ` patchwork-bot+netdevbpf
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=83f3b5c9-ec98-4a70-ace2-1e40187704b3@gmail.com \
--to=mykyta.yatsenko5@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@meta.com \
--cc=kernel-team@meta.com \
--cc=yatsenko@meta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox