From: Jiri Olsa <olsajiri@gmail.com>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
eddyz87@gmail.com, ihor.solodrai@linux.dev,
yonghong.song@linux.dev, song@kernel.org, martin.lau@linux.dev,
memxor@gmail.com, emil@etsalapatis.com, puranjay@kernel.org,
yatsenko@meta.com, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/3] Inline BTF followups
Date: Tue, 13 Oct 2026 09:46:05 +0200 [thread overview]
Message-ID: <as3hvUUPUiPTeaNM@krava> (raw)
In-Reply-To: <20261012140640.2932195-1-alan.maguire@oracle.com>
On Mon, Oct 12, 2026 at 03:06:37PM +0100, Alan Maguire wrote:
> This series addresses lingering issues after BTF inline
> series landed.
>
> Patch 1 fixes validation issue on loading BTF inline info.
>
> Patch 2 corrects the base address calculation for BTF inline
> data in LOCSEC to use the ELF section base rather than module
> base.
>
> Patch 3 enables BTF inline info for CI config.
>
> Alan Maguire (3):
> btf: Fix size/vlen validation for BTF_KIND_LOC_PARAM
> selftests/bpf: Fix btf_inline to use .text section as base
> selftests/bpf: Enable CONFIG_DEBUG_INFO_BTF_INLINE for CI
Acked-by: Jiri Olsa <jolsa@kernel.org>
jirka
>
> kernel/bpf/btf.c | 8 ++++----
> tools/testing/selftests/bpf/config | 1 +
> .../selftests/bpf/prog_tests/btf_inline.c | 5 +++--
> tools/testing/selftests/bpf/trace_helpers.c | 19 +++++++++++++++++++
> tools/testing/selftests/bpf/trace_helpers.h | 1 +
> 5 files changed, 28 insertions(+), 6 deletions(-)
>
> --
> 2.43.5
>
next prev parent reply other threads:[~2026-10-13 7:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 14:06 [PATCH bpf-next 0/3] Inline BTF followups Alan Maguire
2026-10-12 14:06 ` [PATCH bpf-next 1/3] btf: Fix size/vlen validation for BTF_KIND_LOC_PARAM Alan Maguire
2026-10-12 14:49 ` bot+bpf-ci
2026-10-13 7:43 ` Jiri Olsa
2026-10-12 14:06 ` [PATCH bpf-next 2/3] selftests/bpf: Fix btf_inline to use .text section as base Alan Maguire
2026-10-12 14:06 ` [PATCH bpf-next 3/3] selftests/bpf: Enable CONFIG_DEBUG_INFO_BTF_INLINE for CI Alan Maguire
2026-10-13 7:46 ` Jiri Olsa [this message]
2026-10-13 13:50 ` [PATCH bpf-next 0/3] Inline BTF followups 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=as3hvUUPUiPTeaNM@krava \
--to=olsajiri@gmail.com \
--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=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=puranjay@kernel.org \
--cc=song@kernel.org \
--cc=yatsenko@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