From: patchwork-bot+netdevbpf@kernel.org
To: Ning Ding <dingning04@gmail.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/2] bpf: Invalidate RCU pointers after final spin unlock
Date: Tue, 04 Aug 2026 09:40:20 +0000 [thread overview]
Message-ID: <178583642064.3066243.929090840390958892.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260803112615.3362122-1-dingning04@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Mon, 3 Aug 2026 04:26:07 -0700 you wrote:
> In a sleepable BPF program, a spin lock can provide the only RCU protection
> for a kptr. The final spin unlock ends that protection, but the verifier
> leaves the pointer valid. Another CPU can then free the object before the
> pointer is used. A capability-limited runtime PoC triggered a
> KASAN-confirmed task_struct use-after-free.
>
> Patch 1 invalidates RCU-protected pointers only when an unlock leaves the
> final RCU-protected context. Patch 2 adds a negative sleepable test and
> positive controls for non-sleepable and explicit-RCU contexts.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: Invalidate RCU pointers after final spin unlock
https://git.kernel.org/bpf/bpf-next/c/180c7000712d
- [bpf-next,v2,2/2] selftests/bpf: Test RCU pointer invalidation after spin unlock
https://git.kernel.org/bpf/bpf-next/c/bb2df6fd891d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-08-04 9:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 11:26 [PATCH bpf-next v2 0/2] bpf: Invalidate RCU pointers after final spin unlock Ning Ding
2026-08-03 11:26 ` [PATCH bpf-next v2 1/2] " Ning Ding
2026-08-04 9:30 ` Kumar Kartikeya Dwivedi
2026-08-03 11:26 ` [PATCH bpf-next v2 2/2] selftests/bpf: Test RCU pointer invalidation after " Ning Ding
2026-08-04 9:40 ` patchwork-bot+netdevbpf [this message]
2026-08-04 10:50 ` [PATCH bpf-next v2 0/2] bpf: Invalidate RCU pointers after final " Puranjay Mohan
2026-08-04 16:28 ` Paul E. McKenney
2026-08-05 7:00 ` Ning Ding
2026-08-06 9:02 ` Kumar Kartikeya Dwivedi
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=178583642064.3066243.929090840390958892.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dingning04@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 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.