From: Alan Maguire <alan.maguire@oracle.com>
To: andrii@kernel.org
Cc: eddyz87@gmail.com, ast@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, acme@kernel.org, ttreyer@meta.com,
yonghong.song@linux.dev, song@kernel.org,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, ihor.solodrai@linux.dev,
bpf@vger.kernel.org, Alan Maguire <alan.maguire@oracle.com>
Subject: [PATCH v2 bpf-next 0/2] Multi-split BTF fixes and test
Date: Tue, 28 Oct 2025 15:57:07 +0000 [thread overview]
Message-ID: <20251028155709.1265445-1-alan.maguire@oracle.com> (raw)
This small series consists of a fix to multi-split BTF parsing
(patch 1) and a test which exercises (multi-)split BTF parsing
(patch 2).
Changes since v1 [1]
- BPF code-review bot spotted another place that the string offset
needed to be adjusted based upon base start string offset + header
string offset.
- added selftests to extend split BTF testing to parsing
[1] https://lore.kernel.org/bpf/20251023142812.258870-1-alan.maguire@oracle.com/
Alan Maguire (2):
libbpf: Fix parsing of multi-split BTF
selftests/bpf: Test parsing of (multi-)split BTF
tools/lib/bpf/btf.c | 4 +-
.../selftests/bpf/prog_tests/btf_split.c | 71 ++++++++++++++++++-
2 files changed, 72 insertions(+), 3 deletions(-)
--
2.39.3
next reply other threads:[~2025-10-28 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 15:57 Alan Maguire [this message]
2025-10-28 15:57 ` [PATCH v2 bpf-next 1/2] libbpf: Fix parsing of multi-split BTF Alan Maguire
2025-10-28 20:01 ` Andrii Nakryiko
2025-10-28 15:57 ` [PATCH v2 bpf-next 2/2] selftests/bpf: Test parsing of (multi-)split BTF Alan Maguire
2025-10-28 16:45 ` bot+bpf-ci
2025-10-28 20:01 ` Andrii Nakryiko
2025-10-28 20:11 ` Andrii Nakryiko
2025-10-28 22:58 ` Alan Maguire
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=20251028155709.1265445-1-alan.maguire@oracle.com \
--to=alan.maguire@oracle.com \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=ttreyer@meta.com \
--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