From: Eduard Zingerman <eddyz87@gmail.com>
To: Tianci Cao <ziye@zju.edu.cn>
Cc: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, haoluo@google.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
martin.lau@linux.dev, sdf@fomichev.me, shenghaoyuan0928@163.com,
song@kernel.org, tangyazhou518@outlook.com,
yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next v3 2/2] selftests/bpf: Add tests for BPF_END bitwise tracking
Date: Thu, 05 Feb 2026 10:35:41 -0800 [thread overview]
Message-ID: <0e05189fc901cc1952982fe422d11c565f01c7f9.camel@gmail.com> (raw)
In-Reply-To: <20260205052313.225076-1-ziye@zju.edu.cn>
On Thu, 2026-02-05 at 13:23 +0800, Tianci Cao wrote:
[...]
> On a side note, we are also working on range tracking (interval analysis)
> support for bswap operations. While bswap is non-monotonic and hard to
> track with ranges, we found that by leveraging existing range information,
> range tracking can complement bitwise tracking (tnum) to yield a more
> precise combined reg state.
>
> Given that the implementation would be more complex than the tnum approach,
> we wanted to ask if the community would be interested in seeing an RFC for this?
Hi Tianci,
Depends on how complicated the implementation is.
Is it just theoretical work or you see some real-world programs that
fail to verify due to insufficient BPF_END range tracking?
Thanks,
Eduard
[...]
next prev parent reply other threads:[~2026-02-05 18:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 11:15 [PATCH bpf-next v3 0/2] bpf: Add bitwise tracking for BPF_END Tianci Cao
2026-02-04 11:15 ` [PATCH bpf-next v3 1/2] " Tianci Cao
2026-02-04 11:15 ` [PATCH bpf-next v3 2/2] selftests/bpf: Add tests for BPF_END bitwise tracking Tianci Cao
2026-02-04 19:58 ` Eduard Zingerman
2026-02-05 5:23 ` Tianci Cao
2026-02-05 18:35 ` Eduard Zingerman [this message]
2026-02-10 9:44 ` Tianci Cao
2026-02-05 3:14 ` [PATCH bpf-next v3 0/2] bpf: Add bitwise tracking for BPF_END Alexei Starovoitov
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=0e05189fc901cc1952982fe422d11c565f01c7f9.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=shenghaoyuan0928@163.com \
--cc=song@kernel.org \
--cc=tangyazhou518@outlook.com \
--cc=yonghong.song@linux.dev \
--cc=ziye@zju.edu.cn \
/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