From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com
Subject: Re: [PATCH bpf 1/2] bpf: Fix packet range of pointers sharing an id
Date: Thu, 01 Oct 2026 16:50:32 +0000 [thread overview]
Message-ID: <179087343276.3011010.2529405625402472129.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261001145255.855630-1-alexei.starovoitov@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Thu, 1 Oct 2026 14:52:54 +0000 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> Since commit 022ac0750883 ("bpf: use reg->var_off instead of reg->off
> for pointers"), find_good_pkt_pointers() sets the range of all packet
> pointers sharing an id from the umax of the compared pointer, and
> check_packet_access() requires umax + off + size <= range. That assumes
> the umax of two such pointers differ by exactly their constant distance.
> reg_bounds_sync() breaks it when var_off tightens one umax and not the
> other:
>
> [...]
Here is the summary with links:
- [bpf,1/2] bpf: Fix packet range of pointers sharing an id
https://git.kernel.org/bpf/bpf/c/b88822d2584f
- [bpf,2/2] selftests/bpf: Test packet range of pointers sharing an id
https://git.kernel.org/bpf/bpf/c/33a154a96e71
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-10-01 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 14:52 [PATCH bpf 1/2] bpf: Fix packet range of pointers sharing an id Alexei Starovoitov
2026-10-01 14:52 ` [PATCH bpf 2/2] selftests/bpf: Test " Alexei Starovoitov
2026-10-01 16: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=179087343276.3011010.2529405625402472129.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=memxor@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox