From: Song Liu <song@kernel.org>
To: bpf@vger.kernel.org
Cc: kernel-team@meta.com, andrii@kernel.org, eddyz87@gmail.com,
ast@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
Song Liu <song@kernel.org>
Subject: [PATCH v4 bpf-next 0/2] Range tracking for BPF_NEG
Date: Wed, 25 Jun 2025 09:40:23 -0700 [thread overview]
Message-ID: <20250625164025.3310203-1-song@kernel.org> (raw)
Add range tracking for BPF_NEG. Please see commit log of 1/2 for more
details.
---
Changes v3 => v4:
1. Fix selftest verifier_value_ptr_arith.c. (Eduard)
v3: https://lore.kernel.org/bpf/20250624233328.313573-1-song@kernel.org/
Changes v2 => v3:
1. Minor changes in the selftests. (Eduard)
v2: https://lore.kernel.org/bpf/20250624220038.656646-1-song@kernel.org/
Changes v1 => v2:
1. Split new selftests to a separate patch. (Eduard)
2. Reset reg id on BPF_NEG. (Eduard)
3. Use env->fake_reg instead of a bpf_reg_state on the stack. (Eduard)
4. Add __msg for passing selftests.
v1: https://lore.kernel.org/bpf/20250624172320.2923031-1-song@kernel.org/
Song Liu (2):
bpf: Add range tracking for BPF_NEG
selftests/bpf: Add tests for BPF_NEG range tracking logic
include/linux/tnum.h | 2 +
kernel/bpf/tnum.c | 5 ++
kernel/bpf/verifier.c | 17 ++++-
.../bpf/progs/verifier_bounds_deduction.c | 11 +--
.../selftests/bpf/progs/verifier_precision.c | 70 +++++++++++++++++++
.../bpf/progs/verifier_value_ptr_arith.c | 22 ++++--
6 files changed, 116 insertions(+), 11 deletions(-)
--
2.47.1
next reply other threads:[~2025-06-25 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 16:40 Song Liu [this message]
2025-06-25 16:40 ` [PATCH v4 bpf-next 1/2] bpf: Add range tracking for BPF_NEG Song Liu
2025-06-25 17:55 ` Eduard Zingerman
2025-06-25 16:40 ` [PATCH v4 bpf-next 2/2] selftests/bpf: Add tests for BPF_NEG range tracking logic Song Liu
2025-06-25 17:55 ` Eduard Zingerman
2025-06-25 22:20 ` [PATCH v4 bpf-next 0/2] Range tracking for BPF_NEG 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=20250625164025.3310203-1-song@kernel.org \
--to=song@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@meta.com \
--cc=martin.lau@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