From: patchwork-bot+netdevbpf@kernel.org
To: Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
eddyz87@gmail.com, memxor@gmail.com, bpf@vger.kernel.org,
alan.maguire@oracle.com
Subject: Re: [PATCH bpf-next v2 0/5] libbpf: Render decl_tags in btf_dump
Date: Wed, 30 Sep 2026 09:10:15 +0000 [thread overview]
Message-ID: <179075941528.1349208.11059576048812534137.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260929234608.48503-1-ihor.solodrai@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 29 Sep 2026 16:46:03 -0700 you wrote:
> BTF supports arbitrary __attribute__ encoding via decl tags and type
> tags [1]. However btf_dump facility only outputs the attributes
> encoded in BTF as type tags, which was implemented in commit
> 2019c58318b8 ("libbpf: Check the kflag of type tags in btf_dump").
>
> BTF_KIND_DECL_TAG has been left out of btf_dump entirely, independent
> of the kflag value. An attribute a BTF producer encoded is silently
> dropped from the C output.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/5] libbpf: Walk types in btf_dump_resize(), not in mark_referenced()
https://git.kernel.org/bpf/bpf-next/c/1419795b98cf
- [bpf-next,v2,2/5] libbpf: Render decl_tags in btf_dump
https://git.kernel.org/bpf/bpf-next/c/76ea31239021
- [bpf-next,v2,3/5] selftests/bpf: Add ASSERT_TEXT_EQ()
https://git.kernel.org/bpf/bpf-next/c/1c36a1a41a47
- [bpf-next,v2,4/5] selftests/bpf: Test btf_dump rendering of decl_tags
https://git.kernel.org/bpf/bpf-next/c/096ee6e38267
- [bpf-next,v2,5/5] selftests/bpf: Show the tag kflag in the raw BTF dump helper
https://git.kernel.org/bpf/bpf-next/c/2c964f6c5d8e
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-09-30 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 23:46 [PATCH bpf-next v2 0/5] libbpf: Render decl_tags in btf_dump Ihor Solodrai
2026-09-29 23:46 ` [PATCH bpf-next v2 1/5] libbpf: Walk types in btf_dump_resize(), not in mark_referenced() Ihor Solodrai
2026-09-29 23:46 ` [PATCH bpf-next v2 2/5] libbpf: Render decl_tags in btf_dump Ihor Solodrai
2026-09-29 23:46 ` [PATCH bpf-next v2 3/5] selftests/bpf: Add ASSERT_TEXT_EQ() Ihor Solodrai
2026-09-29 23:46 ` [PATCH bpf-next v2 4/5] selftests/bpf: Test btf_dump rendering of decl_tags Ihor Solodrai
2026-09-29 23:46 ` [PATCH bpf-next v2 5/5] selftests/bpf: Show the tag kflag in the raw BTF dump helper Ihor Solodrai
2026-09-30 9:10 ` 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=179075941528.1349208.11059576048812534137.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=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=memxor@gmail.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