From: Luis Vieira <luisflavieira@gmail.com>
To: Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Ihor Solodrai <ihor.solodrai@linux.dev>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>,
Emil Tsalapatis <emil@etsalapatis.com>,
Shuah Khan <shuah@kernel.org>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Luis Vieira <luisflavieira@gmail.com>
Subject: [PATCH bpf-next v2 0/2] libbpf: Fix struct and union zero detection in BTF dumper
Date: Thu, 01 Oct 2026 00:42:57 -0300 [thread overview]
Message-ID: <20261001-libbpf-btf-enodata-fix-v2-0-89f6e8a0240e@gmail.com> (raw)
Fix struct and union zero detection in the BTF dumper and add the
regression coverage in a separate selftest patch.
Changes in v2:
- Split the regression selftest into a separate patch, as requested by
Andrii Nakryiko.
- Link to v1:
https://patch.msgid.link/20260928-libbpf-btf-enodata-fix-v1-1-56dae4cab778@gmail.com
---
Luis Vieira (2):
libbpf: Fix struct and union zero detection in BTF dumper
selftests/bpf: Add regression test for BTF dump zero detection
tools/lib/bpf/btf_dump.c | 2 +-
tools/testing/selftests/bpf/prog_tests/btf_dump.c | 5 +++++
2 files changed, 6 insertions(+), 1 deletion(-)
---
base-commit: 6a75c73eebd4d497ded7d08b47894f9ddbebb5a9
change-id: 20260928-libbpf-btf-enodata-fix-ac6381645ab8
Best regards,
--
Luis Vieira <luisflavieira@gmail.com>
next reply other threads:[~2026-10-01 3:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 3:42 Luis Vieira [this message]
2026-10-01 3:42 ` [PATCH bpf-next v2 1/2] " Luis Vieira
2026-10-01 4:24 ` bot+bpf-ci
2026-10-01 3:42 ` [PATCH bpf-next v2 2/2] selftests/bpf: Add regression test for BTF dump zero detection Luis Vieira
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=20261001-libbpf-btf-enodata-fix-v2-0-89f6e8a0240e@gmail.com \
--to=luisflavieira@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@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
all inboxes | Powered by JetHome®