linux-stable.git/tools/testing/selftests/futex/include, branch linux-6.16.y

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

2025-08-20T16:40:57+00:00

[ Upstream commit 04850819c65c8242072818655d4341e70ae998b5 ]

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 
Signed-off-by: Ben Zong-You Xie 
Signed-off-by: Thomas Gleixner 
Reviewed-by: Muhammad Usama Anjum 
Link: https://lore.kernel.org/all/20250710103630.3156130-1-ben717@andestech.com
Signed-off-by: Sasha Levin

selftests/futex: Convert 32-bit timespec to 64-bit version for 32-bit compatibility mode

2025-07-06T09:15:29+00:00

sys_futex_wait() expects a struct __kernel_timespec pointer for the
timeout, but the provided struct timespec pointer is of type struct
old_timespec32 when compiled for 32-bit architectures, unless they use
64-bit timespecs already.

Make it work for all variants by converting the provided timespec value
into a local struct __kernel_timespec and provide a pointer to it to the
syscall. This is a pointless operation for 64-bit, but this is not a
hotpath operation, so keep it simple.

This fix is based off [1]

Originally-by: Wei Gao 
Signed-off-by: Terry Tritton 
Signed-off-by: Thomas Gleixner 
Link: https://lore.kernel.org/all/20250704190234.14230-1-terry.tritton@linaro.org
Link: https://lore.kernel.org/all/20231203235117.29677-1-wegao@suse.com/ [1]

selftests/futex: Add futex_numa_mpol

2025-05-03T10:02:10+00:00

Test the basic functionality for the NUMA and MPOL flags:
- FUTEX2_NUMA should take the NUMA node which is after the uaddr
  and use it.
- Only update the node if FUTEX_NO_NODE was set by the user
- FUTEX2_MPOL should use the memory based on the policy. I attempted to
  set the node with mbind() and then use this with MPOL but this fails
  and futex falls back to the default node for the current CPU.

Signed-off-by: Sebastian Andrzej Siewior 
Signed-off-by: Peter Zijlstra (Intel) 
Link: https://lore.kernel.org/r/20250416162921.513656-22-bigeasy@linutronix.de

selftests/futex: Build without headers nonsense

2025-05-03T10:02:10+00:00

Make it build without relying on recent headers.

Signed-off-by: Peter Zijlstra (Intel)

selftests: futex: Add sys_futex_waitv() test

2021-10-07T11:51:12+00:00

Create a new file to test the waitv mechanism. Test both private and
shared futexes. Wake the last futex in the array, and check if the
return value from futex_waitv() is the right index.

Signed-off-by: André Almeida 
Signed-off-by: Peter Zijlstra (Intel) 
Link: https://lore.kernel.org/r/20210923171111.300673-20-andrealmeid@collabora.com

treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 152

2019-05-30T18:26:32+00:00

Based on 1 normalized pattern(s):

  this program is free software you can redistribute it and or modify
  it under the terms of the gnu general public license as published by
  the free software foundation either version 2 of the license or at
  your option any later version

extracted by the scancode license scanner the SPDX license identifier

  GPL-2.0-or-later

has been chosen to replace the boilerplate/reference in 3029 file(s).

Signed-off-by: Thomas Gleixner 
Reviewed-by: Allison Randal 
Cc: linux-spdx@vger.kernel.org
Link: https://lkml.kernel.org/r/20190527070032.746973796@linutronix.de
Signed-off-by: Greg Kroah-Hartman

selftests: futex: convert test to use ksft TAP13 framework

2017-08-16T23:45:00+00:00

Convert test to use ksft TAP13 framework to print user friendly
test output which is consistent across kselftest suite.

Acked-by: Darren Hart (VMware) 
Signed-off-by: Shuah Khan

selftests: futex: print testcase-name and PASS/FAIL/ERROR status

2017-06-07T16:07:21+00:00

Most of the tests under selftests follow a pattern for their results,
which can then be parsed easily by other external tools easily. Though
futex tests do print the test results very well, it doesn't really
follow the general selftests pattern.

This patch makes necessary changes to fix that.

Output before this patch:
futex_requeue_pi: Test requeue functionality
        Arguments: broadcast=0 locked=0 owner=0 timeout=0ns
Result:  PASS

Output after this patch:
futex_requeue_pi: Test requeue functionality
        Arguments: broadcast=0 locked=0 owner=0 timeout=0ns
selftests: futex-requeue-pi [PASS]

Signed-off-by: Naresh Kamboju 
Signed-off-by: Shuah Khan

selftests/futex: Add stdio used for logging

2017-01-19T17:30:15+00:00

Fix missing printf compile warnings.

Signed-off-by: Stafford Horne 
Signed-off-by: Shuah Khan

selftests/futex: Increment ksft pass and fail counters

2015-05-26T21:58:08+00:00

Add kselftest.h to logging.h and increment the pass and fail counters as
part of the print_result routine which is called by all futex tests.

Cc: Shuah Khan 
Cc: linux-api@vger.kernel.org
Cc: Ingo Molnar 
Cc: Peter Zijlstra 
Cc: Thomas Gleixner 
Cc: Davidlohr Bueso 
Cc: KOSAKI Motohiro 
Signed-off-by: Darren Hart 
Signed-off-by: Shuah Khan