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

selftests/futex: Add futex_numa to .gitignore

2025-07-06T07:39:01+00:00

futex_numa was never added to the .gitignore file.
Add it.

Fixes: 9140f57c1c13 ("futex,selftests: Add another FUTEX2_NUMA selftest")
Signed-off-by: Terry Tritton 
Signed-off-by: Thomas Gleixner 
Reviewed-by: André Almeida 
Link: https://lore.kernel.org/all/20250704103749.10341-1-terry.tritton@linaro.org

selftests/futex: Set the home_node in futex_numa_mpol

2025-06-05T12:37:58+00:00

The test fails at the MPOL step if multiple nodes are available. The
reason is that mbind() sets the policy but the home_node, which is
retrieved by the futex code, is not set. This causes to retrieve the
current node and with multiple nodes it fails on one of the iterations.

Use numa_set_mempolicy_home_node() to set the expected node.
Use ksft_exit_fail_msg() to fail and exit in order not to confuse ktap.

Fixes: 3163369407baf ("selftests/futex: Add futex_numa_mpol")
Suggested-by: Vlastimil Babka 
Signed-off-by: Sebastian Andrzej Siewior 
Signed-off-by: Peter Zijlstra (Intel) 
Link: https://lkml.kernel.org/r/20250528085521.1938355-3-bigeasy@linutronix.de

selftests/futex: getopt() requires int as return value.

2025-06-05T12:37:58+00:00

Mark reported that futex_priv_hash fails on ARM64.
It turns out that the command line parsing does not terminate properly
and ends in the default case assuming an invalid option was passed.

Use an int as the return type for getopt().

Closes: https://lore.kernel.org/all/31869a69-063f-44a3-a079-ba71b2506cce@sirena.org.uk/
Fixes: 3163369407baf ("selftests/futex: Add futex_numa_mpol")
Fixes: cda95faef7bcf ("selftests/futex: Add futex_priv_hash")
Reported-by: Mark Brown 
Signed-off-by: Sebastian Andrzej Siewior 
Signed-off-by: Peter Zijlstra (Intel) 
Link: https://lkml.kernel.org/r/20250528085521.1938355-2-bigeasy@linutronix.de

selftests/futex: Fix spelling mistake "unitiliazed" -> "uninitialized"

2025-05-21T11:57:41+00:00

There is a spelling mistake in a fail error message. Fix it.

Signed-off-by: Colin Ian King 
Signed-off-by: Peter Zijlstra (Intel) 
Reviewed-by: Sebastian Andrzej Siewior 
Link: https://lore.kernel.org/r/20250520080657.30726-1-colin.i.king@gmail.com

tools headers: Synchronize prctl.h ABI header

2025-05-21T11:57:41+00:00

The prctl.h ABI header was slightly updated during the development of
the interface. In particular the "immutable" parameter became a bit in
the option argument.

Synchronize prctl.h ABI header again and make use of the definition in
the testsuite and "perf bench futex".

Signed-off-by: Sebastian Andrzej Siewior 
Signed-off-by: Peter Zijlstra (Intel) 
Reviewed-by: André Almeida 
Link: https://lore.kernel.org/r/20250517151455.1065363-5-bigeasy@linutronix.de

selftests/futex: Use TAP output in futex_numa_mpol

2025-05-21T11:57:40+00:00

Use TAP output for easier automated testing.

Suggested-by: André Almeida 
Signed-off-by: Sebastian Andrzej Siewior 
Signed-off-by: Peter Zijlstra (Intel) 
Reviewed-by: André Almeida 
Link: https://lore.kernel.org/r/20250517151455.1065363-3-bigeasy@linutronix.de

selftests/futex: Use TAP output in futex_priv_hash

2025-05-21T11:57:40+00:00

Use TAP output for easier automated testing.

Suggested-by: André Almeida 
Signed-off-by: Sebastian Andrzej Siewior 
Signed-off-by: Peter Zijlstra (Intel) 
Reviewed-by: André Almeida 
Link: https://lore.kernel.org/r/20250517151455.1065363-2-bigeasy@linutronix.de

futex,selftests: Add another FUTEX2_NUMA selftest

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

Implement a simple NUMA aware spinlock for testing and howto purposes.

Signed-off-by: Peter Zijlstra (Intel)

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: Add futex_priv_hash

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

Test the basic functionality of the private hash:
- Upon start, with no threads there is no private hash.
- The first thread initializes the private hash.
- More than four threads will increase the size of the private hash if
  the system has more than 16 CPUs online.
- Once the user sets the size of private hash, auto scaling is disabled.
- The user is only allowed to use numbers to the power of two.
- The user may request the global or make the hash immutable.
- Once the global hash has been set or the hash has been made immutable,
  further changes are not allowed.
- Futex operations should work the whole time. It must be possible to
  hold a lock, such a PI initialised mutex, during the resize operation.

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