From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: bpf@vger.kernel.org, wanghai8081@gmail.com, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, eddyz87@gmail.com,
memxor@gmail.com, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, jolsa@kernel.org, emil@etsalapatis.com,
ihor.solodrai@linux.dev, alan.maguire@oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2] libbpf: Fix stale raw data after btf__relocate()
Date: Tue, 03 Nov 2026 18:10:04 +0000 [thread overview]
Message-ID: <179372940480.1794115.11055566429963645138.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261103081836.381430-1-jiayuan.chen@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 3 Nov 2026 16:18:35 +0800 you wrote:
> btf_relocate() rewrites type ids in place but doesn't drop the cached
> raw_data, so btf__raw_data() after btf__relocate() returns the old
> bytes with pre-relocation ids.
>
> Only modifiable BTF keeps raw_data as a cache. For read-only BTF, e.g.
> module BTF relocated in btf_parse_elf(), types_data points into
> raw_data and is already rewritten in place, so it must not be freed.
> Make btf_invalidate_raw_data() tell the two apart and call it from
> btf__relocate(). Also recompute named_start_id since start_id changes
> after relocation, like the kernel does.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] libbpf: Fix stale raw data after btf__relocate()
https://git.kernel.org/bpf/bpf-next/c/b2bb14d8035d
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-11-03 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 8:18 Jiayuan Chen
2026-11-03 18: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=179372940480.1794115.11055566429963645138.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=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jiayuan.chen@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=song@kernel.org \
--cc=wanghai8081@gmail.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
all inboxes | Powered by JetHome®