From: patchwork-bot+netdevbpf@kernel.org
To: Paul Chaignon <paul.chaignon@gmail.com>
Cc: bpf@vger.kernel.org, harishankar.vishwanathan@gmail.com,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, shung-hsi.yu@suse.com,
srinivas.narayana@rutgers.edu, santosh.nagarakatte@rutgers.edu
Subject: Re: [PATCH bpf-next v3 0/6] Fix invariant violations and improve branch detection
Date: Fri, 03 Apr 2026 01:30:13 +0000 [thread overview]
Message-ID: <177517981379.692254.1576029739396503335.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1775142354.git.paul.chaignon@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 2 Apr 2026 17:07:25 +0200 you wrote:
> This patchset fixes invariant violations on register bounds. These
> invariant violations cause a warning and happen when reg_bounds_sync is
> trying to refine register bounds while walking an impossible branch.
>
> This patchset takes this situation as an opportunity to improve
> verification performance. That is, the verifier will use the invariant
> violations as a signal that a branch cannot be taken and process it as
> dead code.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/6] bpf: Refactor reg_bounds_sanity_check
https://git.kernel.org/bpf/bpf-next/c/a1311b94ef85
- [bpf-next,v3,2/6] bpf: Use bpf_verifier_env buffers for reg_set_min_max
https://git.kernel.org/bpf/bpf-next/c/ec1d77cb0ee9
- [bpf-next,v3,3/6] bpf: Exit early if reg_bounds_sync gets invalid inputs
https://git.kernel.org/bpf/bpf-next/c/a2a14e874b4e
- [bpf-next,v3,4/6] bpf: Simulate branches to prune based on range violations
https://git.kernel.org/bpf/bpf-next/c/b254c6d816e5
- [bpf-next,v3,5/6] selftests/bpf: Cover invariant violation case from syzbot
https://git.kernel.org/bpf/bpf-next/c/2ba199067b89
- [bpf-next,v3,6/6] selftests/bpf: Remove invariant violation flags
https://git.kernel.org/bpf/bpf-next/c/7cbded6ed98f
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-04-03 1:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 15:07 [PATCH bpf-next v3 0/6] Fix invariant violations and improve branch detection Paul Chaignon
2026-04-02 15:08 ` [PATCH bpf-next v3 1/6] bpf: Refactor reg_bounds_sanity_check Paul Chaignon
2026-04-03 0:53 ` Eduard Zingerman
2026-04-02 15:09 ` [PATCH bpf-next v3 2/6] bpf: Use bpf_verifier_env buffers for reg_set_min_max Paul Chaignon
2026-04-02 15:10 ` [PATCH bpf-next v3 3/6] bpf: Exit early if reg_bounds_sync gets invalid inputs Paul Chaignon
2026-04-03 0:54 ` Eduard Zingerman
2026-04-02 15:10 ` [PATCH bpf-next v3 4/6] bpf: Simulate branches to prune based on range violations Paul Chaignon
2026-04-02 16:28 ` bot+bpf-ci
2026-04-02 16:33 ` Paul Chaignon
2026-04-03 1:05 ` Eduard Zingerman
2026-04-02 15:11 ` [PATCH bpf-next v3 5/6] selftests/bpf: Cover invariant violation case from syzbot Paul Chaignon
2026-04-02 15:12 ` [PATCH bpf-next v3 6/6] selftests/bpf: Remove invariant violation flags Paul Chaignon
2026-04-03 1:08 ` [PATCH bpf-next v3 0/6] Fix invariant violations and improve branch detection Eduard Zingerman
2026-04-03 1:30 ` 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=177517981379.692254.1576029739396503335.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=harishankar.vishwanathan@gmail.com \
--cc=paul.chaignon@gmail.com \
--cc=santosh.nagarakatte@rutgers.edu \
--cc=shung-hsi.yu@suse.com \
--cc=srinivas.narayana@rutgers.edu \
/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