From: sashiko-bot@kernel.org
To: "Florent Revest (Anthropic)" <florent.revest@linux.dev>
Cc: "Heiko Carstens" <hca@linux.ibm.com>,
linux-s390@vger.kernel.org, "Vasily Gorbik" <gor@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf v5 1/3] bpf: Wait for an RCU tasks grace period before freeing trampoline progs
Date: Sat, 26 Sep 2026 14:07:06 +0000 [thread overview]
Message-ID: <20260926140707.2069B1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260926135605.1217928-2-florent.revest@linux.dev>
> When a prog is detached from a trampoline, it is freed after an RCU
> grace period, or an RCU tasks trace one if it is sleepable. This covers
> the tasks that are running the prog, since the prog's enter helper takes
> the matching read lock before the prog is called. On a preemptible
> kernel, it doesn't cover a task that was preempted in the trampoline
> just before the enter helper. That task holds no lock yet, and it calls
> the prog after it was freed:
>
> BUG: KASAN: vmalloc-out-of-bounds in __bpf_prog_enter_recur+0x3a5/0x3f0
> Read of size 8 at addr ffffc90000055040 by task candidate/110
> CPU: 1 UID: 0 PID: 110 Comm: candidate Not tainted 7.3.0-rc2-00014-g15071f2a1263-dirty #2 PREEMPT(full)
> Call Trace:
> <TASK>
> __bpf_prog_enter_recur+0x3a5/0x3f0
> bpf_trampoline_6442509193+0x37/0xf1
> [ ... ]
> Fixes: e21aa341785c ("bpf: Fix fexit trampoline.")
> Reported-by: Junseo Lim <zirajs7@gmail.com>
> Closes: https://lore.kernel.org/bpf/aqdrwVpanH3WGurX@omen-arch/
> Assisted-by: Claude:unspecified
> Signed-off-by: Florent Revest (Anthropic) <florent.revest@linux.dev>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260926135605.1217928-1-florent.revest@linux.dev?part=1
next prev parent reply other threads:[~2026-09-26 14:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 13:55 [PATCH bpf v5 0/3] bpf: Fix use-after-free of progs detached from busy trampolines Florent Revest (Anthropic)
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-26 13:55 ` Florent Revest (Anthropic)
2026-09-26 14:07 ` sashiko-bot [this message]
2026-09-27 20:41 ` bot+bpf-ci
2026-09-27 20:41 ` bot+bpf-ci
2026-09-27 20:41 ` bot+bpf-ci
2026-09-28 8:50 ` Florent Revest
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:55 ` Florent Revest (Anthropic)
2026-09-26 14:09 ` sashiko-bot
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-26 13:56 ` Florent Revest (Anthropic)
2026-09-26 14:01 ` sashiko-bot
2026-09-29 6:20 ` [PATCH bpf v5 0/3] bpf: Fix use-after-free of progs detached from busy trampolines patchwork-bot+netdevbpf
2026-09-29 6:20 ` 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=20260926140707.2069B1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=florent.revest@linux.dev \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=sashiko-reviews@lists.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.