From: Paul Chaignon <paul.chaignon@gmail.com>
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Harishankar Vishwanathan <harishankar.vishwanathan@gmail.com>,
Srinivas Narayana <srinivas.narayana@rutgers.edu>,
Santosh Nagarakatte <santosh.nagarakatte@rutgers.edu>
Subject: Re: [PATCH v3 bpf 0/4] Fix invariant violation for single-value tnums
Date: Thu, 26 Mar 2026 00:51:24 +0100 [thread overview]
Message-ID: <acR0_ORJWmaN1L2P@Tunnel> (raw)
In-Reply-To: <4e6dd64a162b3cab3635706ae6abfdd0be4db5db.camel@gmail.com>
On Mon, Mar 23, 2026 at 11:02:43AM -0700, Eduard Zingerman wrote:
> On Fri, 2026-02-27 at 22:30 +0100, Paul Chaignon wrote:
[...]
> The verifier produces a more precise result here because of additional
> information inferred by tnum_step: lower 32-bits can be equal to zero
> only for r7 value of 0xffffffff00000000.
>
> Which implies that reg_bounds* test logic needs further adjustment.
> Could you please take a look? Please let me know if you see any viable
> routes to amend this test.
Hi Eduard,
Thanks for the report! I wasn't aware of this slow mode. I'll take a
look when back from vacation, on Monday.
Paul
>
> Thanks,
> Eduard
prev parent reply other threads:[~2026-03-25 23:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 21:30 [PATCH v3 bpf 0/4] Fix invariant violation for single-value tnums Paul Chaignon
2026-02-27 21:32 ` [PATCH v3 bpf 1/4] bpf: Introduce tnum_step to step through tnum's members Paul Chaignon
2026-02-27 21:35 ` [PATCH v3 bpf 2/4] bpf: Improve bounds when tnum has a single possible value Paul Chaignon
2026-02-27 21:36 ` [PATCH v3 bpf 3/4] selftests/bpf: Test refinement of single-value tnum Paul Chaignon
2026-02-27 21:42 ` [PATCH v3 bpf 4/4] selftests/bpf: Avoid simplification of crafted bounds test Paul Chaignon
2026-02-28 0:30 ` [PATCH v3 bpf 0/4] Fix invariant violation for single-value tnums patchwork-bot+netdevbpf
2026-03-23 18:02 ` Eduard Zingerman
2026-03-25 23:51 ` Paul Chaignon [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=acR0_ORJWmaN1L2P@Tunnel \
--to=paul.chaignon@gmail.com \
--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=santosh.nagarakatte@rutgers.edu \
--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