From: patchwork-bot+netdevbpf@kernel.org
To: Yiyang Chen <chenyy23@mails.tsinghua.edu.cn>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, john.fastabend@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, shuah@kernel.org, emil@etsalapatis.com,
ihor.solodrai@linux.dev, shung-hsi.yu@suse.com,
danjwade95@gmail.com, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf v4 0/4] bpf: Preserve pointer state for commuted arithmetic
Date: Fri, 31 Jul 2026 19:50:11 +0000 [thread overview]
Message-ID: <178552741189.880156.9331013283819113501.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260729-c3-035-public-bpf-v4-v4-0-8ee297e2346b@mails.tsinghua.edu.cn>
Hello:
This series was applied to bpf/bpf.git (master)
by Eduard Zingerman <eddyz87@gmail.com>:
On Wed, 29 Jul 2026 15:18:26 +0000 you wrote:
> This series fixes pointer-state propagation for commuted scalar += pointer
> arithmetic in the verifier.
>
> Patch 1 simplifies sanitize_err() before the pointer-state change. Patch 2
> keeps the full pointer register state when the pointer operand is the source
> of the add, preserving fields such as the stack frame number and parent id.
> Patch 3 moves the untrusted PTR_TO_MEM early return after state propagation,
> so scalar += untrusted_pointer remains usable through the probe-read path.
> Patch 4 adds verifier selftests for stack frame number preservation,
> readonly-untrusted memory access, and dynptr data-slice invalidation.
>
> [...]
Here is the summary with links:
- [bpf,v4,1/4] bpf: simplify sanitize_err() signature
https://git.kernel.org/bpf/bpf/c/a15970d916b3
- [bpf,v4,2/4] bpf: Preserve pointer state for commuted arithmetic
https://git.kernel.org/bpf/bpf/c/a4c6f804b44c
- [bpf,v4,3/4] bpf: Propagate untrusted pointer state in commuted arithmetic
https://git.kernel.org/bpf/bpf/c/cdf19b1b3c01
- [bpf,v4,4/4] selftests/bpf: Cover commuted pointer state propagation
https://git.kernel.org/bpf/bpf/c/21596761ff37
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-07-31 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 15:18 [PATCH bpf v4 0/4] bpf: Preserve pointer state for commuted arithmetic Yiyang Chen via B4 Relay
2026-07-29 15:18 ` [PATCH bpf v4 1/4] bpf: simplify sanitize_err() signature Yiyang Chen via B4 Relay
2026-07-30 8:22 ` Shung-Hsi Yu
2026-07-29 15:18 ` [PATCH bpf v4 2/4] bpf: Preserve pointer state for commuted arithmetic Yiyang Chen via B4 Relay
2026-07-30 8:25 ` Shung-Hsi Yu
2026-07-29 15:18 ` [PATCH bpf v4 3/4] bpf: Propagate untrusted pointer state in " Yiyang Chen via B4 Relay
2026-07-29 15:18 ` [PATCH bpf v4 4/4] selftests/bpf: Cover commuted pointer state propagation Yiyang Chen via B4 Relay
2026-07-31 19:50 ` 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=178552741189.880156.9331013283819113501.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=chenyy23@mails.tsinghua.edu.cn \
--cc=daniel@iogearbox.net \
--cc=danjwade95@gmail.com \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--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=shung-hsi.yu@suse.com \
--cc=song@kernel.org \
--cc=yonghong.song@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox