From: Zhenzhong Wu <jt26wzz@gmail.com>
To: bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, menglong8.dong@gmail.com,
eddyz87@gmail.com, shung-hsi.yu@suse.com, tamird@kernel.org
Subject: [RFC PATCH 6.1.y 2/2] bpf: make the verifier tracks the "not equal" for regs
Date: Tue, 2 Jun 2026 02:04:00 +0800 [thread overview]
Message-ID: <20260601180400.1381736-3-jt26wzz@gmail.com> (raw)
In-Reply-To: <20260601180400.1381736-1-jt26wzz@gmail.com>
[ Upstream commit d028f87517d6775dccff4ddbca2740826f9e53f1 ]
We can derive some new information for BPF_JNE in regs_refine_cond_op().
Take following code for example:
/* The type of "a" is u32 */
if (a > 0 && a < 100) {
/* the range of the register for a is [0, 99], not [1, 99],
* and will cause the following error:
*
* invalid zero-sized read
*
* as a can be 0.
*/
bpf_skb_store_bytes(skb, xx, xx, a, 0);
}
In the code above, "a > 0" will be compiled to "jmp xxx if a == 0". In the
TRUE branch, the dst_reg will be marked as known to 0. However, in the
fallthrough(FALSE) branch, the dst_reg will not be handled, which makes
the [min, max] for a is [0, 99], not [1, 99].
For BPF_JNE, we can reduce the range of the dst reg if the src reg is a
const and is exactly the edge of the dst reg.
Signed-off-by: Menglong Dong <menglong8.dong@gmail.com>
Acked-by: Andrii Nakryiko <andrii@kernel.org>
Acked-by: Shung-Hsi Yu <shung-hsi.yu@suse.com>
Link: https://lore.kernel.org/r/20231219134800.1550388-2-menglong8.dong@gmail.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
[ zhenzhong: adapt to 6.1.y reg_set_min_max() layout. The upstream
change lives in regs_refine_cond_op(); 6.1.y still refines true/false
branch states in reg_set_min_max(), so apply the not-equal range
exclusion to BPF_JEQ's false_reg and BPF_JNE's true_reg there. ]
Signed-off-by: Zhenzhong Wu <jt26wzz@gmail.com>
---
kernel/bpf/verifier.c | 32 ++++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+)
diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
index 5e029d1..e51f44b 100644
--- a/kernel/bpf/verifier.c
+++ b/kernel/bpf/verifier.c
@@ -9954,18 +9954,50 @@ static void reg_set_min_max(struct bpf_reg_state *true_reg,
if (is_jmp32) {
__mark_reg32_known(true_reg, val32);
true_32off = tnum_subreg(true_reg->var_off);
+ if (false_reg->u32_min_value == val32)
+ false_reg->u32_min_value++;
+ if (false_reg->u32_max_value == val32)
+ false_reg->u32_max_value--;
+ if (false_reg->s32_min_value == sval32)
+ false_reg->s32_min_value++;
+ if (false_reg->s32_max_value == sval32)
+ false_reg->s32_max_value--;
} else {
___mark_reg_known(true_reg, val);
true_64off = true_reg->var_off;
+ if (false_reg->umin_value == val)
+ false_reg->umin_value++;
+ if (false_reg->umax_value == val)
+ false_reg->umax_value--;
+ if (false_reg->smin_value == sval)
+ false_reg->smin_value++;
+ if (false_reg->smax_value == sval)
+ false_reg->smax_value--;
}
break;
case BPF_JNE:
if (is_jmp32) {
__mark_reg32_known(false_reg, val32);
false_32off = tnum_subreg(false_reg->var_off);
+ if (true_reg->u32_min_value == val32)
+ true_reg->u32_min_value++;
+ if (true_reg->u32_max_value == val32)
+ true_reg->u32_max_value--;
+ if (true_reg->s32_min_value == sval32)
+ true_reg->s32_min_value++;
+ if (true_reg->s32_max_value == sval32)
+ true_reg->s32_max_value--;
} else {
___mark_reg_known(false_reg, val);
false_64off = false_reg->var_off;
+ if (true_reg->umin_value == val)
+ true_reg->umin_value++;
+ if (true_reg->umax_value == val)
+ true_reg->umax_value--;
+ if (true_reg->smin_value == sval)
+ true_reg->smin_value++;
+ if (true_reg->smax_value == sval)
+ true_reg->smax_value--;
}
break;
case BPF_JSET:
--
2.43.0
next prev parent reply other threads:[~2026-06-01 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 18:03 [RFC PATCH 6.1.y 0/2] bpf: backport scalar not-equal tracking fixes Zhenzhong Wu
2026-06-01 18:03 ` [RFC PATCH 6.1.y 1/2] bpf: drop knowledge-losing __reg_combine_{32,64}_into_{64,32} logic Zhenzhong Wu
2026-06-01 18:04 ` Zhenzhong Wu [this message]
2026-06-02 5:47 ` [RFC PATCH 6.1.y 0/2] bpf: backport scalar not-equal tracking fixes Shung-Hsi Yu
2026-06-02 6:42 ` Shung-Hsi Yu
2026-06-02 9:17 ` Shung-Hsi Yu
2026-06-02 17:25 ` Zhenzhong Wu
2026-06-06 9:19 ` Shung-Hsi Yu
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=20260601180400.1381736-3-jt26wzz@gmail.com \
--to=jt26wzz@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=menglong8.dong@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=shung-hsi.yu@suse.com \
--cc=song@kernel.org \
--cc=tamird@kernel.org \
--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
all inboxes | Powered by JetHome®