From: patchwork-bot+netdevbpf@kernel.org
To: Florent Revest <florent.revest@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
memxor@gmail.com, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, kpsingh@kernel.org, john.fastabend@gmail.com,
leon.hwang@linux.dev, zirajs7@gmail.com, rhkrqnwk98@gmail.com,
puranjay@kernel.org, xukuohai@huaweicloud.com, iii@linux.ibm.com,
hbathini@linux.ibm.com, chleroy@kernel.org, naveen@kernel.org,
bjorn@kernel.org, pulehui@huawei.com, yangtiezhu@loongson.cn,
hengqi.chen@gmail.com, linux-kernel@vger.kernel.org,
aou@eecs.berkeley.edu, agordeev@linux.ibm.com, alex@ghiti.fr,
bp@alien8.de, catalin.marinas@arm.com, borntraeger@linux.ibm.com,
dave.hansen@linux.intel.com, emil@etsalapatis.com,
hca@linux.ibm.com, hpa@zytor.com, chenhuacai@kernel.org,
ihor.solodrai@linux.dev, mingo@redhat.com,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org,
loongarch@lists.linux.dev, maddy@linux.ibm.com,
mark.rutland@arm.com, mpe@ellerman.id.au, npiggin@gmail.com,
palmer@dabbelt.com, paulmck@kernel.org, pjw@kernel.org,
ritesh.list@gmail.com, sshegde@linux.ibm.com, shuah@kernel.org,
svens@linux.ibm.com, tglx@kernel.org, gor@linux.ibm.com,
kernel@xen0n.name, will@kernel.org, x86@kernel.org
Subject: Re: [PATCH bpf v5 0/3] bpf: Fix use-after-free of progs detached from busy trampolines
Date: Tue, 29 Sep 2026 06:20:28 +0000 [thread overview]
Message-ID: <179066282803.293113.8557815551946775052.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260926135605.1217928-1-florent.revest@linux.dev>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 26 Sep 2026 13:55:57 +0000 you wrote:
> A task running in a trampoline image can call a prog that was detached
> and freed in the meantime, when it slept in a sleepable prog before
> reaching the detached one or was preempted right before calling it.
> Patch 1 handles the preempted case with an RCU tasks grace period,
> patch 2 handles the sleeping case by patching detached progs out of the
> images that still call them and patch 3 adds a selftest for the sleeping
> case.
>
> [...]
Here is the summary with links:
- [bpf,v5,1/3] bpf: Wait for an RCU tasks grace period before freeing trampoline progs
https://git.kernel.org/bpf/bpf/c/0fb5751a6e41
- [bpf,v5,2/3] bpf: Skip detached progs in trampoline images that are still in use
https://git.kernel.org/bpf/bpf/c/17637e1a581a
- [bpf,v5,3/3] selftests/bpf: Detach a trampoline prog while a task sleeps before it
https://git.kernel.org/bpf/bpf/c/d5288c519bbd
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-09-29 6:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 13:55 Florent Revest (Anthropic)
2026-09-26 13:55 ` [PATCH bpf v5 1/3] bpf: Wait for an RCU tasks grace period before freeing trampoline progs Florent Revest (Anthropic)
2026-09-27 20:41 ` bot+bpf-ci
2026-09-28 8:50 ` Florent Revest
2026-09-26 13:55 ` [PATCH bpf v5 2/3] bpf: Skip detached progs in trampoline images that are still in use Florent Revest (Anthropic)
2026-09-26 13:56 ` [PATCH bpf v5 3/3] selftests/bpf: Detach a trampoline prog while a task sleeps before it Florent Revest (Anthropic)
2026-09-29 6:20 ` 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=179066282803.293113.8557815551946775052.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=alex@ghiti.fr \
--cc=andrii@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=chleroy@kernel.org \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@linux.intel.com \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=florent.revest@linux.dev \
--cc=gor@linux.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hengqi.chen@gmail.com \
--cc=hpa@zytor.com \
--cc=ihor.solodrai@linux.dev \
--cc=iii@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel@xen0n.name \
--cc=kpsingh@kernel.org \
--cc=leon.hwang@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=maddy@linux.ibm.com \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paulmck@kernel.org \
--cc=pjw@kernel.org \
--cc=pulehui@huawei.com \
--cc=puranjay@kernel.org \
--cc=rhkrqnwk98@gmail.com \
--cc=ritesh.list@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=sshegde@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=tglx@kernel.org \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=xukuohai@huaweicloud.com \
--cc=yangtiezhu@loongson.cn \
--cc=yonghong.song@linux.dev \
--cc=zirajs7@gmail.com \
/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®