From: Paul Chaignon <paul.chaignon@gmail.com>
To: bot+bpf-ci@kernel.org
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,
martin.lau@kernel.org, yonghong.song@linux.dev, clm@meta.com,
ihor.solodrai@linux.dev
Subject: Re: [PATCH bpf-next v3 4/6] bpf: Simulate branches to prune based on range violations
Date: Thu, 2 Apr 2026 18:33:32 +0200 [thread overview]
Message-ID: <ac6aXEuufxIYKgO5@mail.gmail.com> (raw)
In-Reply-To: <3f23feac390f144ec5e47178bcc0ca5cb774e093d2d1ce6675b0b31fb4c9c95e@mail.kernel.org>
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
next prev parent reply other threads:[~2026-04-02 16:33 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 [this message]
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
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=ac6aXEuufxIYKgO5@mail.gmail.com \
--to=paul.chaignon@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bot+bpf-ci@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clm@meta.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=harishankar.vishwanathan@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=martin.lau@kernel.org \
--cc=santosh.nagarakatte@rutgers.edu \
--cc=shung-hsi.yu@suse.com \
--cc=srinivas.narayana@rutgers.edu \
--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