From: Vineet Gupta <vineet.gupta@linux.dev>
To: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com
Cc: martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
john.fastabend@gmail.com, shuah@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Vineet Gupta <vineet.gupta@linux.dev>
Subject: [PATCH bpf-next v3 10/12] selftests/bpf: Cover the low-32 link for narrowing stack fills
Date: Tue, 20 Oct 2026 09:19:05 -0700 [thread overview]
Message-ID: <20261020161907.2115379-11-vineet.gupta@linux.dev> (raw)
In-Reply-To: <20261020161907.2115379-1-vineet.gupta@linux.dev>
Eight programs, following the mov set:
- zext_fill_narrow_from_wide_spill: narrowing the spilled value reaches
the filled register
- sext_fill_narrow_from_wide_spill: the same for a sign-extending fill
- sext_delta_survives_narrowing_fill: a slot carrying a delta hands it
to the fill, so r2 is (u32)(r6 + 5) and not (u32)r6
- zext_fill_full_width_keeps_full_link: a full-width fill stays a plain
64-bit equality
- zext_fill_byte_forms_no_link: a sub-word fill is below the model
- fill_kinds_reach_different_values: the same, for the two kinds off one
slot
- sext_fill_does_not_inherit_zext_link: a sign-extending fill must not
come away with the slot's zero-extending link
- sext_byte_fill_drops_sext_link: nor may an 8-bit ldsx keep a
sign-extending one
The first three pin the link itself: disabling link formation in the fill
arm makes all three fail. The last two pin the link-kind checks in
check_mem_access() and assert on the register dump rather than a guarded
branch, so they fail on the rule rather than a downstream effect.
The sign-extending fills are ldsx, so they sit under a new CAN_USE_LDSX
gate; verifier_ldsx.c open-coded the same condition and uses the macro
now. sext_byte_fill_drops_sext_link needs both gates, since the
BPF_REG_LINK_SEXT it tests is built with a movsx and only the fill is an
ldsx.
Signed-off-by: Vineet Gupta <vineet.gupta@linux.dev>
---
v3: was v2 10/13.
- new: sext_delta_survives_narrowing_fill, for the inherited delta
- new: sext_fill_does_not_inherit_zext_link and
sext_byte_fill_drops_sext_link, for the two kinds a sign-extending
load must not come away with. Both assert on the register dump
rather than a guarded branch.
- the sign-extending fills are ldsx, so they sit under a new
CAN_USE_LDSX gate; verifier_ldsx.c open-coded the same condition and
uses the macro now.
tools/testing/selftests/bpf/progs/bpf_misc.h | 8 +
.../selftests/bpf/progs/verifier_ldsx.c | 8 +-
.../bpf/progs/verifier_linked_scalars.c | 306 ++++++++++++++++++
3 files changed, 316 insertions(+), 6 deletions(-)
diff --git a/tools/testing/selftests/bpf/progs/bpf_misc.h b/tools/testing/selftests/bpf/progs/bpf_misc.h
index c5ffb36dfd74..ef0250a10cc7 100644
--- a/tools/testing/selftests/bpf/progs/bpf_misc.h
+++ b/tools/testing/selftests/bpf/progs/bpf_misc.h
@@ -293,6 +293,14 @@
#define CAN_USE_MOVSX
#endif
+#if (defined(__TARGET_ARCH_arm64) || defined(__TARGET_ARCH_x86) || \
+ (defined(__TARGET_ARCH_riscv) && __riscv_xlen == 64) || \
+ defined(__TARGET_ARCH_arm) || defined(__TARGET_ARCH_s390) || \
+ defined(__TARGET_ARCH_loongarch)) && \
+ (__clang_major__ >= 18 || defined(__BPF_FEATURE_LDSX))
+#define CAN_USE_LDSX
+#endif
+
#if __clang_major__ >= 18 && defined(ENABLE_ATOMICS_TESTS) && \
(defined(__TARGET_ARCH_arm64) || \
defined(__TARGET_ARCH_x86) || \
diff --git a/tools/testing/selftests/bpf/progs/verifier_ldsx.c b/tools/testing/selftests/bpf/progs/verifier_ldsx.c
index 49e8cd4bb4f9..6c1553059101 100644
--- a/tools/testing/selftests/bpf/progs/verifier_ldsx.c
+++ b/tools/testing/selftests/bpf/progs/verifier_ldsx.c
@@ -5,11 +5,7 @@
#include "bpf_misc.h"
#include <bpf_arena_common.h>
-#if (defined(__TARGET_ARCH_arm64) || defined(__TARGET_ARCH_x86) || \
- (defined(__TARGET_ARCH_riscv) && __riscv_xlen == 64) || \
- defined(__TARGET_ARCH_arm) || defined(__TARGET_ARCH_s390) || \
- defined(__TARGET_ARCH_loongarch)) && \
- (__clang_major__ >= 18 || defined(__BPF_FEATURE_LDSX))
+#ifdef CAN_USE_LDSX
SEC("socket")
__description("LDSX, S8")
@@ -464,6 +460,6 @@ int dummy_test(void)
return 0;
}
-#endif
+#endif /* CAN_USE_LDSX */
char _license[] SEC("license") = "GPL";
diff --git a/tools/testing/selftests/bpf/progs/verifier_linked_scalars.c b/tools/testing/selftests/bpf/progs/verifier_linked_scalars.c
index 69efe1381eca..ab78285153fb 100644
--- a/tools/testing/selftests/bpf/progs/verifier_linked_scalars.c
+++ b/tools/testing/selftests/bpf/progs/verifier_linked_scalars.c
@@ -245,6 +245,7 @@ l0_%=: \
: __imm(bpf_get_prandom_u32)
: __clobber_all);
}
+
#endif /* CAN_USE_MOVSX */
SEC("socket")
@@ -1120,6 +1121,102 @@ __naked void zext_mov_breaks_linked_src(void)
: __clobber_all);
}
+/*
+ * A narrowing fill keeps only the slot's low 32 bits, so a later narrowing of
+ * the spilled value must still reach the filled register. Same relation as a
+ * 32-bit mov from a wide source, with the stack slot as the base.
+ */
+SEC("socket")
+__success
+__naked void zext_fill_narrow_from_wide_spill(void)
+{
+ asm volatile (" \
+ call %[bpf_get_prandom_u32]; \
+ r6 = r0; \
+ call %[bpf_get_prandom_u32]; \
+ r0 <<= 32; \
+ r6 |= r0; /* r6 = full 64-bit unknown */ \
+ *(u64 *)(r10 - 8) = r6; /* slot linked to r6 */ \
+"
+#if __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
+" r2 = *(u32 *)(r10 - 8); /* narrowing fill, forms the link */ \
+"
+#else
+" r2 = *(u32 *)(r10 - 4); \
+"
+#endif
+" if w6 != 0 goto 1f; /* narrows r6, propagates to r2 */ \
+ if r2 == 0 goto 1f; \
+ r0 /= 0; \
+1: \
+ r0 = 0; \
+ exit; \
+" :
+ : __imm(bpf_get_prandom_u32)
+ : __clobber_all);
+}
+
+/*
+ * A full-width fill of a wide slot is a plain 64-bit equality, not a low-32
+ * link, so it must keep propagating exactly as before.
+ */
+SEC("socket")
+__success
+__naked void zext_fill_full_width_keeps_full_link(void)
+{
+ asm volatile (" \
+ call %[bpf_get_prandom_u32]; \
+ r6 = r0; \
+ call %[bpf_get_prandom_u32]; \
+ r0 <<= 32; \
+ r6 |= r0; \
+ *(u64 *)(r10 - 8) = r6; \
+ r2 = *(u64 *)(r10 - 8); /* no narrowing */ \
+ if r6 != 0 goto 1f; \
+ if r2 == 0 goto 1f; \
+ r0 /= 0; \
+1: \
+ r0 = 0; \
+ exit; \
+" :
+ : __imm(bpf_get_prandom_u32)
+ : __clobber_all);
+}
+
+/*
+ * A sub-word fill is below the low-32 model, so no link is formed and the
+ * relation is dropped as before.
+ */
+SEC("socket")
+__failure __msg("div by zero")
+__naked void zext_fill_byte_forms_no_link(void)
+{
+ asm volatile (" \
+ call %[bpf_get_prandom_u32]; \
+ r6 = r0; \
+ call %[bpf_get_prandom_u32]; \
+ r0 <<= 32; \
+ r6 |= r0; \
+ *(u64 *)(r10 - 8) = r6; \
+"
+#if __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
+" r2 = *(u8 *)(r10 - 8); /* 1-byte fill: no link */ \
+"
+#else
+" r2 = *(u8 *)(r10 - 1); \
+"
+#endif
+" if w6 != 0 goto 1f; \
+ if r2 == 0 goto 1f; /* not deduced */ \
+ r0 /= 0; \
+1: \
+ r0 = 0; \
+ exit; \
+" :
+ : __imm(bpf_get_prandom_u32)
+ : __clobber_all);
+}
+
#ifdef CAN_USE_MOVSX
/*
@@ -1494,6 +1591,215 @@ __naked void sext_drops_stale_step(void)
: __clobber_all);
}
+/*
+ * Same for a narrowing fill: the slot is (s32)(r6 + 5), so the filled register
+ * is (u32)(r6 + 5). Forcing the delta to 0 made the verifier believe r2 == r6.
+ */
+SEC("socket")
+__success
+__naked void sext_delta_survives_narrowing_fill(void)
+{
+ asm volatile (" \
+ call %[bpf_get_prandom_u32]; \
+ r6 = r0; \
+ r6 <<= 32; \
+ call %[bpf_get_prandom_u32]; \
+ r6 |= r0; /* r6 = full 64-bit unknown */ \
+ w7 = w6; /* BPF_REG_LINK_ZEXT, delta 0 */ \
+ w7 += 5; /* BPF_REG_LINK_ZEXT, delta 5 */ \
+ r8 = (s32)r7; /* BPF_REG_LINK_SEXT, delta 5 */ \
+ *(u64 *)(r10 - 8) = r8; /* full spill keeps the link */ \
+"
+#if __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
+" r2 = *(u32 *)(r10 - 8); /* narrowing fill inherits delta */ \
+"
+#else
+" r2 = *(u32 *)(r10 - 4); \
+"
+#endif
+" if r6 != 0 goto 1f; /* r6 == 0, so r2 == 5 */ \
+ if r2 == 5 goto 1f; /* always taken: r2 is 5 */ \
+ r0 /= 0; \
+1: \
+ r0 = 0; \
+ exit; \
+" :
+ : __imm(bpf_get_prandom_u32)
+ : __clobber_all);
+}
+
#endif /* CAN_USE_MOVSX */
+#ifdef CAN_USE_LDSX
+
+/*
+ * The sign-extending counterpart: the filled register is the sign extension of
+ * the slot's low 32 bits, so a narrowing of those bits arrives sign-extended.
+ */
+SEC("socket")
+__success
+__naked void sext_fill_narrow_from_wide_spill(void)
+{
+ asm volatile (" \
+ call %[bpf_get_prandom_u32]; \
+ r6 = r0; \
+ call %[bpf_get_prandom_u32]; \
+ r0 <<= 32; \
+ r6 |= r0; /* r6 = full 64-bit unknown */ \
+ *(u64 *)(r10 - 8) = r6; /* slot linked to r6 */ \
+"
+#if __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
+" r2 = *(s32 *)(r10 - 8); /* narrowing sx fill */ \
+"
+#else
+" r2 = *(s32 *)(r10 - 4); \
+"
+#endif
+" if w6 != -1 goto 1f; /* narrows r6, propagates to r2 */ \
+ if r2 == -1 goto 1f; /* sign-extended, not 0xffffffff */ \
+ r0 /= 0; \
+1: \
+ r0 = 0; \
+ exit; \
+" :
+ : __imm(bpf_get_prandom_u32)
+ : __clobber_all);
+}
+
+/*
+ * The same, for the two link kinds off one slot.
+ */
+SEC("socket")
+__failure __msg("div by zero")
+__flag(BPF_F_TEST_STATE_FREQ)
+__naked void fill_kinds_reach_different_values(void)
+{
+ asm volatile (" \
+ call %[bpf_get_prandom_u32]; \
+ r6 = r0; \
+ r6 &= 1; \
+ call %[bpf_get_prandom_u32]; \
+ r8 = r0; \
+ call %[bpf_get_prandom_u32]; \
+ r0 <<= 32; \
+ r8 |= r0; \
+ *(u64 *)(r10 - 8) = r8; \
+ if r6 >= 1 goto 2f; \
+"
+#if __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
+" r2 = *(s32 *)(r10 - 8); /* sign-extending fill */ \
+"
+#else
+" r2 = *(s32 *)(r10 - 4); \
+"
+#endif
+" goto 1f; \
+2: \
+"
+#if __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
+" r2 = *(u32 *)(r10 - 8); /* zero-extending fill */ \
+"
+#else
+" r2 = *(u32 *)(r10 - 4); \
+"
+#endif
+"1: \
+ if w8 != -1 goto 3f; \
+ if r2 == -1 goto 3f; /* only the sign-extending path */ \
+ r0 /= 0; \
+3: \
+ r0 = 0; \
+ exit; \
+" :
+ : __imm(bpf_get_prandom_u32)
+ : __clobber_all);
+}
+
+/*
+ * A sign-extending fill must not come away with a zero-extending link. The
+ * slot below already fits 32 bits, so the fill is not narrowing and assigns
+ * no link kind of its own, and "state->regs[dst] = *reg" copies the slot's
+ * verbatim; check_mem_access() is what has to drop it, since it would leave
+ * r2 recording a zero-extension of a value it has just sign-extended.
+ * Asserted on the register dump rather than on a guarded branch, so it pins
+ * the rule itself and not a downstream effect.
+ */
+SEC("socket")
+__success __log_level(2)
+/* a copied link would print as R2=scalar(id=N+0,smin=... */
+__msg("(81) r2 = *(s32 *)(r10 {{.*}} R2=scalar(smin=")
+__naked void sext_fill_does_not_inherit_zext_link(void)
+{
+ asm volatile (" \
+ call %[bpf_get_prandom_u32]; \
+ r6 = r0; \
+ call %[bpf_get_prandom_u32]; \
+ r0 <<= 32; \
+ r6 |= r0; /* r6 = full 64-bit unknown */ \
+ w7 = w6; /* r7 = zext32(r6), fits 32 bits */ \
+ *(u64 *)(r10 - 8) = r7; \
+"
+#if __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
+" r2 = *(s32 *)(r10 - 8); /* sign-extending, not narrowing */ \
+"
+#else
+" r2 = *(s32 *)(r10 - 4); \
+"
+#endif
+" r0 = 0; \
+ exit; \
+" :
+ : __imm(bpf_get_prandom_u32)
+ : __clobber_all);
+}
+
+/*
+ * BPF_REG_LINK_SEXT says the register is (s32)(base + delta) -- a 32-bit sign
+ * extension specifically. An 8- or 16-bit ldsx is a different relation, so
+ * the exemption that keeps a sign-extending link across a sign-extending
+ * load has to be gated on the load width. Ungated, r2 below claims to be
+ * (s32)r6 when it is really (s8)((s32)r6).
+ */
+SEC("socket")
+__success __log_level(2)
+#ifdef CAN_USE_MOVSX
+/*
+ * Needs MOVSX as well as LDSX: the BPF_REG_LINK_SEXT under test is built with
+ * r7 = (s32)r6, and only the byte fill below is an ldsx.
+ */
+/* a surviving link would print as R2=scalar(id=N+0.sx,smin=... */
+__msg("(91) r2 = *(s8 *)(r10 {{.*}} R2=scalar(smin=")
+__naked void sext_byte_fill_drops_sext_link(void)
+{
+ asm volatile (" \
+ call %[bpf_get_prandom_u32]; \
+ r6 = r0; \
+ call %[bpf_get_prandom_u32]; \
+ r0 <<= 32; \
+ r6 |= r0; /* r6 = full 64-bit unknown */ \
+ r7 = (s32)r6; /* r7 = BPF_REG_LINK_SEXT, delta 0 */ \
+ if r7 > 255 goto 1f; /* r7 fits a byte */ \
+ *(u64 *)(r10 - 8) = r7; /* full spill keeps the link */ \
+"
+#if __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
+" r2 = *(s8 *)(r10 - 8); /* 8-bit ldsx: no link survives */ \
+"
+#else
+" r2 = *(s8 *)(r10 - 1); \
+"
+#endif
+" r0 = r2; /* keep r2 live so the fill prints it */ \
+ r0 &= 1; \
+ exit; \
+1: \
+ r0 = 0; \
+ exit; \
+" :
+ : __imm(bpf_get_prandom_u32)
+ : __clobber_all);
+}
+#endif /* CAN_USE_MOVSX */
+
+#endif /* CAN_USE_LDSX */
+
char _license[] SEC("license") = "GPL";
--
2.53.0-Meta
next prev parent reply other threads:[~2026-10-20 16:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 16:18 [PATCH bpf-next v3 00/12] bpf: track scalar equality across the low 32 bits Vineet Gupta
2026-10-20 16:18 ` [PATCH bpf-next v3 01/12] bpf: Keep the 32-bit range across a sign extension that cannot change it Vineet Gupta
2026-10-20 16:18 ` [PATCH bpf-next v3 02/12] selftests/bpf: Cover sign extensions that cannot change the range Vineet Gupta
2026-10-20 16:18 ` [PATCH bpf-next v3 03/12] bpf: Prepare linked scalars for relations narrower than 64 bits Vineet Gupta
2026-10-20 16:18 ` [PATCH bpf-next v3 04/12] bpf: Track low-32 scalar equality across zero-extending movs Vineet Gupta
2026-10-20 16:19 ` [PATCH bpf-next v3 05/12] selftests/bpf: Cover the low-32 link for " Vineet Gupta
2026-10-20 16:19 ` [PATCH bpf-next v3 06/12] bpf: Track low-32 scalar equality across sign-extending movs Vineet Gupta
2026-10-20 16:19 ` [PATCH bpf-next v3 07/12] selftests/bpf: Cover the low-32 link for " Vineet Gupta
2026-10-20 16:19 ` [PATCH bpf-next v3 08/12] bpf: Recover the low 32 bits on the reverse link direction Vineet Gupta
2026-10-20 16:19 ` [PATCH bpf-next v3 09/12] bpf: Track low-32 scalar equality across narrowing stack fills Vineet Gupta
2026-10-20 16:19 ` Vineet Gupta [this message]
2026-10-20 16:19 ` [PATCH bpf-next v3 11/12] [do not merge] bpf: Track low-32 scalar equality across narrowing stack spills Vineet Gupta
2026-10-20 16:19 ` [PATCH bpf-next v3 12/12] [do not merge] selftests/bpf: Cover the low-32 link for " Vineet Gupta
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=20261020161907.2115379-11-vineet.gupta@linux.dev \
--to=vineet.gupta@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@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