From: patchwork-bot+netdevbpf@kernel.org
To: Paul Chaignon <paul.chaignon@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, yonghong.song@linux.dev,
shung-hsi.yu@suse.com
Subject: Re: [PATCH bpf-next v4 0/5] bpf: Improve 64bits bounds refinement
Date: Mon, 28 Jul 2025 17:10:14 +0000 [thread overview]
Message-ID: <175372261425.782645.17863794939852326898.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1753695655.git.paul.chaignon@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 28 Jul 2025 11:50:01 +0200 you wrote:
> This patchset improves the 64bits bounds refinement when the s64 ranges
> crosses the sign boundary. The first patch explains the small addition
> to __reg64_deduce_bounds. The last one explains why we need a third
> round of __reg_deduce_bounds. The third patch adds a selftest with a
> more complete example of the impact on verification. The second and
> fourth patches update the existing selftests to take the new refinement
> into account.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/5] bpf: Improve bounds when s64 crosses sign boundary
https://git.kernel.org/bpf/bpf-next/c/00bf8d0c6c9b
- [bpf-next,v4,2/5] selftests/bpf: Update reg_bound range refinement logic
https://git.kernel.org/bpf/bpf-next/c/da653de268d3
- [bpf-next,v4,3/5] selftests/bpf: Test cross-sign 64bits range refinement
https://git.kernel.org/bpf/bpf-next/c/26e5e346a52c
- [bpf-next,v4,4/5] selftests/bpf: Test invariants on JSLT crossing sign
https://git.kernel.org/bpf/bpf-next/c/f96841bbf4a1
- [bpf-next,v4,5/5] bpf: Add third round of bounds deduction
https://git.kernel.org/bpf/bpf-next/c/5dbb19b16ac4
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-07-28 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 9:50 [PATCH bpf-next v4 0/5] bpf: Improve 64bits bounds refinement Paul Chaignon
2025-07-28 9:50 ` [PATCH bpf-next v4 1/5] bpf: Improve bounds when s64 crosses sign boundary Paul Chaignon
2025-07-28 9:51 ` [PATCH bpf-next v4 2/5] selftests/bpf: Update reg_bound range refinement logic Paul Chaignon
2025-07-28 9:51 ` [PATCH bpf-next v4 3/5] selftests/bpf: Test cross-sign 64bits range refinement Paul Chaignon
2025-07-28 9:51 ` [PATCH bpf-next v4 4/5] selftests/bpf: Test invariants on JSLT crossing sign Paul Chaignon
2025-07-28 9:52 ` [PATCH bpf-next v4 5/5] bpf: Add third round of bounds deduction Paul Chaignon
2025-07-28 17:10 ` 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=175372261425.782645.17863794939852326898.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=paul.chaignon@gmail.com \
--cc=shung-hsi.yu@suse.com \
--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 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.