linux-kernel - [tip: locking/futex] selftests/futex: Define SYS_futex on 32-bit architectures with 64-bit time

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <175317656648.1420.2526056310701166486.tip-bot2@tip-bot2>
Date: Tue, 22 Jul 2025 09:29:26 -0000
From: "tip-bot2 for Cynthia Huang" <tip-bot2@...utronix.de>
To: linux-tip-commits@...r.kernel.org
Cc: Cynthia Huang <cynthia@...estech.com>,
 "Ben Zong-You Xie" <ben717@...estech.com>,
 Thomas Gleixner <tglx@...utronix.de>,
 Muhammad Usama Anjum <usama.anjum@...labora.com>, x86@...nel.org,
 linux-kernel@...r.kernel.org
Subject: [tip: locking/futex] selftests/futex: Define SYS_futex on 32-bit
 architectures with 64-bit time_t

The following commit has been merged into the locking/futex branch of tip:

Commit-ID:     04850819c65c8242072818655d4341e70ae998b5
Gitweb:        https://git.kernel.org/tip/04850819c65c8242072818655d4341e70ae998b5
Author:        Cynthia Huang <cynthia@...estech.com>
AuthorDate:    Thu, 10 Jul 2025 18:36:30 +08:00
Committer:     Thomas Gleixner <tglx@...utronix.de>
CommitterDate: Tue, 22 Jul 2025 11:18:43 +02:00

selftests/futex: Define SYS_futex on 32-bit architectures with 64-bit time_t

The kernel does not provide sys_futex() on 32-bit architectures that do not
support 32-bit time representations, such as riscv32.

As a result, glibc cannot define SYS_futex, causing compilation failures in
tests that rely on this syscall. Define SYS_futex as SYS_futex_time64 in
such cases to ensure successful compilation and compatibility.

Signed-off-by: Cynthia Huang <cynthia@...estech.com>
Signed-off-by: Ben Zong-You Xie <ben717@...estech.com>
Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
Reviewed-by: Muhammad Usama Anjum <usama.anjum@...labora.com>
Link: https://lore.kernel.org/all/20250710103630.3156130-1-ben717@andestech.com

---
 tools/testing/selftests/futex/include/futextest.h | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/tools/testing/selftests/futex/include/futextest.h b/tools/testing/selftests/futex/include/futextest.h
index ddbcfc9..7a5fd1d 100644
--- a/tools/testing/selftests/futex/include/futextest.h
+++ b/tools/testing/selftests/futex/include/futextest.h
@@ -47,6 +47,17 @@ typedef volatile u_int32_t futex_t;
 					 FUTEX_PRIVATE_FLAG)
 #endif
 
+/*
+ * SYS_futex is expected from system C library, in glibc some 32-bit
+ * architectures (e.g. RV32) are using 64-bit time_t, therefore it doesn't have
+ * SYS_futex defined but just SYS_futex_time64. Define SYS_futex as
+ * SYS_futex_time64 in this situation to ensure the compilation and the
+ * compatibility.
+ */
+#if !defined(SYS_futex) && defined(SYS_futex_time64)
+#define SYS_futex SYS_futex_time64
+#endif
+
 /**
  * futex() - SYS_futex syscall wrapper
  * @uaddr:	address of first futex