From: Emil Tsalapatis <emil@etsalapatis.com>
To: bpf@vger.kernel.org
Cc: ast@kernel.org, andrii@kernel.org, eddyz87@gmail.com,
memxor@gmail.com, daniel@iogearbox.net,
Emil Tsalapatis <emil@etsalapatis.com>
Subject: [PATCH bpf-next v2 4/4] selftests/bpf: libarena: Make zero variable type __u32 instead of u32
Date: Tue, 27 Oct 2026 19:24:13 +0000 [thread overview]
Message-ID: <20261027192413.5038-5-emil@etsalapatis.com> (raw)
In-Reply-To: <20261027192413.5038-1-emil@etsalapatis.com>
Change the zero variable used for loop convergence to the user-visible
__u32 type to avoid missing type issues when including the skeleton
in userspace.
Signed-off-by: Emil Tsalapatis <emil@etsalapatis.com>
---
tools/testing/selftests/bpf/libarena/include/libarena/common.h | 2 +-
tools/testing/selftests/bpf/libarena/src/common.bpf.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/testing/selftests/bpf/libarena/include/libarena/common.h b/tools/testing/selftests/bpf/libarena/include/libarena/common.h
index a6220355a697..940e82cc2928 100644
--- a/tools/testing/selftests/bpf/libarena/include/libarena/common.h
+++ b/tools/testing/selftests/bpf/libarena/include/libarena/common.h
@@ -43,7 +43,7 @@ struct {
* imprecise. To force the variable to be imprecise, initialize it with
* the opaque volatile variable 0 instead of the constant 0.
*/
-volatile u32 zero __weak;
+volatile __u32 zero __weak;
extern volatile u64 asan_violated;
int arena_fls(__u64 word);
diff --git a/tools/testing/selftests/bpf/libarena/src/common.bpf.c b/tools/testing/selftests/bpf/libarena/src/common.bpf.c
index d859bd538c52..c3c5326d8ca2 100644
--- a/tools/testing/selftests/bpf/libarena/src/common.bpf.c
+++ b/tools/testing/selftests/bpf/libarena/src/common.bpf.c
@@ -7,7 +7,7 @@
#include <libarena/buddy.h>
struct buddy __arena buddy;
-volatile u32 zero = 0;
+volatile __u32 zero = 0;
/*
* Storage for the queue nodes declared by bpf_arena_spin_lock.h. Each program
--
2.52.0
next prev parent reply other threads:[~2026-10-27 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 19:24 [PATCH bpf-next v2 0/4] selftests/bpf: libarena: compatibility fixups Emil Tsalapatis
2026-10-27 19:24 ` [PATCH bpf-next v2 1/4] libarena: remove in-code licenses Emil Tsalapatis
2026-10-27 19:24 ` [PATCH bpf-next v2 2/4] selftests/bpf: libarena: make allocator growth on alloc failure optional Emil Tsalapatis
2026-10-27 19:24 ` [PATCH bpf-next v2 3/4] selftests/bpf: libarena: add explicit buddy_grow() call Emil Tsalapatis
2026-10-27 19:24 ` Emil Tsalapatis [this message]
2026-10-28 18:50 ` [PATCH bpf-next v2 0/4] selftests/bpf: libarena: compatibility fixups 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=20261027192413.5038-5-emil@etsalapatis.com \
--to=emil@etsalapatis.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=memxor@gmail.com \
/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