Re: [PATCH bpf-next v3 4/6] bpf: Simulate branches to prune based on range violations

Paul Chaignon
2026-04-02T16:33:37Z

On Thu, Apr 02, 2026 at 04:28:30PM +0000, bot+bpf-ci@kernel.org wrote:
> > Reported-by: syzbot+c950cc277150935cc0b5@syzkaller.appspotmail.com
> > Closes: https://syzkaller.appspot.com/bug?extid=c950cc277150935cc0b5
>
> This is a bug fix addressing verifier invariant violations (e.g.
> umax < umin) triggered by syzbot. The v1 of this patch included a
> Fixes: tag pointing to 5f99f312bd3b ("bpf: add register bounds sanity
> checks and sanitization"), which was dropped after discussion about
> whether it pointed to the root cause or the detection mechanism.
>
> Would it make sense to include a Fixes: tag here? Even if 5f99f312bd3b
> only surfaced the issue, having a tag helps stable backport tooling
> identify where the fix is needed. Without it, automated stable processes
> may not pick this up.

We discussed it and considered it best to just drop the tag. We believe
the automated stable processes will likely still pick this up
automatically, and if not, we can always backport ourselves if we want.

>
> https://lore.kernel.org/bpf/swmeukekw55emiwcduoq4jpjk6hwqk7nzxbcs4xgw4mir5ldd7@mqyinrubwmlo/
>
>
> ---
> AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
> See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md
>
> CI run summary: https://github.com/kernel-patches/bpf/actions/runs/23908257980