From: "Kumar Kartikeya Dwivedi" <memxor@gmail.com>
To: "Leon Hwang" <hffilwlqm@gmail.com>,
<patchwork-bot+netdevbpf@kernel.org>,
"Alexei Starovoitov" <alexei.starovoitov@gmail.com>
Cc: <bpf@vger.kernel.org>, <daniel@iogearbox.net>,
<andrii@kernel.org>, <eddyz87@gmail.com>
Subject: Re: [PATCH bpf-next 0/2] bpf: Reject BTF ids with the same address in tracing_multi link
Date: Mon, 12 Oct 2026 10:45:14 +0200 [thread overview]
Message-ID: <DM2Q7S9925AD.3JJZRRIWRSAFE@gmail.com> (raw)
In-Reply-To: <6c732e69-0878-4bf8-80ec-47e40bbedc6f@gmail.com>
On Mon Oct 12, 2026 at 10:26 AM CEST, Leon Hwang wrote:
> On 12/10/26 13:30, patchwork-bot+netdevbpf@kernel.org wrote:
>> Hello:
>>
>> This series was applied to bpf/bpf-next.git (master)
>> by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
>>
>> On Sun, 11 Oct 2026 16:48:34 +0000 you wrote:
>>> From: Alexei Starovoitov <ast@kernel.org>
>>>
>>> tracing_multi link accepts different BTF ids that resolve to the same
>>> address. The attach succeeds, the detach fails in ftrace and the kernel
>>> crashes in freed trampoline images.
>>> 'test_progs -t tracing_multi' hits it when the kernel is built with
>>> CONFIG_DEBUG_INFO_BTF_INLINE. Without it the ids of aliased functions do
>>> the same.
>>>
>>> [...]
>>
>> Here is the summary with links:
>> - [bpf-next,1/2] bpf: Reject BTF ids with the same address in tracing_multi link
>> https://git.kernel.org/bpf/bpf-next/c/7211c18d7ee5
>> - [bpf-next,2/2] selftests/bpf: Test tracing_multi link with BTF ids of the same address
>> https://git.kernel.org/bpf/bpf-next/c/60e84b9127f6
>>
>> You are awesome, thank you!
>
>
> Oops, the applied commits did not collect my Acked-by tags.
>
> Pls collect the Acked-by tags from Jiri and me.
>
Fixed and force pushed.
> Thanks,
> Leon
next prev parent reply other threads:[~2026-10-12 8:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 16:48 [PATCH bpf-next 0/2] bpf: Reject BTF ids with the same address in tracing_multi link Alexei Starovoitov
2026-10-11 16:48 ` [PATCH bpf-next 1/2] " Alexei Starovoitov
2026-10-11 16:48 ` [PATCH bpf-next 2/2] selftests/bpf: Test tracing_multi link with BTF ids of the same address Alexei Starovoitov
2026-10-11 18:15 ` bot+bpf-ci
2026-10-11 18:45 ` Alexei Starovoitov
2026-10-12 4:59 ` [PATCH bpf-next 0/2] bpf: Reject BTF ids with the same address in tracing_multi link Leon Hwang
2026-10-12 5:30 ` patchwork-bot+netdevbpf
2026-10-12 8:26 ` Leon Hwang
2026-10-12 8:45 ` Kumar Kartikeya Dwivedi [this message]
2026-10-12 8:09 ` Jiri Olsa
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=DM2Q7S9925AD.3JJZRRIWRSAFE@gmail.com \
--to=memxor@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=hffilwlqm@gmail.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
/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