From: patchwork-bot+netdevbpf@kernel.org
To: Puranjay Mohan <puranjay@kernel.org>
Cc: bpf@vger.kernel.org, kkd@meta.com, ast@kernel.org,
andrii@kernel.org, daniel@iogearbox.net, martin.lau@kernel.org,
eddyz87@gmail.com, puranjay12@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH bpf-next v2 0/2] bpf: Nested rcu critical sections
Date: Sat, 22 Nov 2025 03:20:10 +0000 [thread overview]
Message-ID: <176378161001.2671115.14700810886503055578.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251117200411.25563-1-puranjay@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 17 Nov 2025 20:04:08 +0000 you wrote:
> v1: https://lore.kernel.org/bpf/20250916113622.19540-1-puranjay@kernel.org/
> Changes in v1->v2:
> - Move the addition of new tests to a separate patch (Alexei)
> - Avoid incrementing active_rcu_locks at two places (Eduard)
>
> Support nested rcu critical sections by making the boolean flag
> active_rcu_lock a counter and use it to manage rcu critical section
> state. bpf_rcu_read_lock() increments this counter and
> bpf_rcu_read_unlock() decrements it, MEM_RCU -> PTR_UNTRUSTED transition
> happens when active_rcu_locks drops to 0.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: support nested rcu critical sections
https://git.kernel.org/bpf/bpf-next/c/4167096cb964
- [bpf-next,v2,2/2] selftests: bpf: Add tests for unbalanced rcu_read_lock
https://git.kernel.org/bpf/bpf-next/c/cf49ec5705a6
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:[~2025-11-22 3:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 20:04 [PATCH bpf-next v2 0/2] bpf: Nested rcu critical sections Puranjay Mohan
2025-11-17 20:04 ` [PATCH bpf-next v2 1/2] bpf: support nested " Puranjay Mohan
2025-11-22 1:13 ` Eduard Zingerman
2025-11-17 20:04 ` [PATCH bpf-next v2 2/2] selftests: bpf: Add tests for unbalanced rcu_read_lock Puranjay Mohan
2025-11-22 1:17 ` Eduard Zingerman
2025-11-22 3: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=176378161001.2671115.14700810886503055578.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--cc=kkd@meta.com \
--cc=martin.lau@kernel.org \
--cc=puranjay12@gmail.com \
--cc=puranjay@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