From: patchwork-bot+netdevbpf@kernel.org
To: Ning Ding <dingning04@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
shuah@kernel.org, zhouchuyi@bytedance.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/2] bpf: Compare iterator types during state pruning
Date: Tue, 11 Aug 2026 22:00:15 +0000 [thread overview]
Message-ID: <178648561523.1170542.5254278257474503414.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260811035955.132989-1-dingning04@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Eduard Zingerman <eddyz87@gmail.com>:
On Mon, 10 Aug 2026 20:59:53 -0700 you wrote:
> Iterator stack slots can be marked MEM_RCU or PTR_UNTRUSTED. The
> STACK_ITER check in stacksafe() does not compare this type, so state
> pruning can treat these states as equal and prune an unsafe path.
>
> Compare the type and add a test where RCU protection has a gap.
>
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: Compare iterator types during state pruning
https://git.kernel.org/bpf/bpf-next/c/83608e303b95
- [bpf-next,v2,2/2] selftests/bpf: Test RCU iterator state pruning
https://git.kernel.org/bpf/bpf-next/c/81f209d5f743
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-08-11 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 3:59 [PATCH bpf-next v2 0/2] bpf: Compare iterator types during state pruning Ning Ding
2026-08-11 3:59 ` [PATCH bpf-next v2 1/2] " Ning Ding
2026-08-11 3:59 ` [PATCH bpf-next v2 2/2] selftests/bpf: Test RCU iterator " Ning Ding
2026-08-11 4:41 ` bot+bpf-ci
2026-08-11 21:54 ` Eduard Zingerman
2026-08-11 22:00 ` 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=178648561523.1170542.5254278257474503414.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=dingning04@gmail.com \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
--cc=zhouchuyi@bytedance.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