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, qmo@kernel.org,
bpf@vger.kernel.org, alan.maguire@oracle.com,
yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next v1 1/3] Revert "libbpf: Fix use-after-free in btf__add_type"
Date: Sat, 07 Nov 2026 00:50:05 +0000 [thread overview]
Message-ID: <179401260543.959208.4014028648619759075.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261106195730.2623973-1-ihor.solodrai@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Fri, 6 Nov 2026 12:57:28 -0700 you wrote:
> This reverts commit 9abe2c42ecab6c86b54838d2d645ca2e10204606.
>
> The commit made btf_rewrite_str() make every base of the destination
> modifiable before taking a pointer to the source string, because
> looking the string up in a base made it modifiable and freed its raw
> data. Since commit efeb5ab5753d ("libbpf: Look up BTF strings without
> making BTF modifiable"), the lookup leaves the raw data in place, so
> the pointer stays valid.
>
> [...]
Here is the summary with links:
- [bpf-next,v1,1/3] Revert "libbpf: Fix use-after-free in btf__add_type"
https://git.kernel.org/bpf/bpf-next/c/2210e69db721
- [bpf-next,v1,2/3] libbpf: Drop btf_dump details from the BTF docs
https://git.kernel.org/bpf/bpf-next/c/9736b748ee82
- [bpf-next,v1,3/3] bpftool: Replace the type tag override table with two checks
https://git.kernel.org/bpf/bpf-next/c/ad6472e01a5f
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-07 0:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 19:57 [PATCH bpf-next v1 1/3] Revert "libbpf: Fix use-after-free in btf__add_type" Ihor Solodrai
2026-11-06 19:57 ` [PATCH bpf-next v1 2/3] libbpf: Drop btf_dump details from the BTF docs Ihor Solodrai
2026-11-06 19:57 ` [PATCH bpf-next v1 3/3] bpftool: Replace the type tag override table with two checks Ihor Solodrai
2026-11-07 0:50 ` 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=179401260543.959208.4014028648619759075.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 \
--cc=qmo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.