linux.git/tools/testing/selftests/futex/functional/futex_wait_timeout.c, branch vsnprintf

selftests/futex: Order calls to futex_lock_pi

2023-08-16T16:48:10+00:00

Observed occassional failures in the futex_wait_timeout test:

ok 1 futex_wait relative succeeds
ok 2 futex_wait_bitset realtime succeeds
ok 3 futex_wait_bitset monotonic succeeds
ok 4 futex_wait_requeue_pi realtime succeeds
ok 5 futex_wait_requeue_pi monotonic succeeds
not ok 6 futex_lock_pi realtime returned 0
......

The test expects the child thread to complete some steps before
the parent thread gets to run. There is an implicit expectation
of the order of invocation of futex_lock_pi between the child thread
and the parent thread. Make this order explicit. If the order is
not met, the futex_lock_pi call in the parent thread succeeds and
will not timeout.

Fixes: f4addd54b161 ("selftests: futex: Expand timeout test")
Signed-off-by: Nysal Jan K.A 
Signed-off-by: Shuah Khan

selftests: futex: Test sys_futex_waitv() timeout

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

Test if the futex_waitv timeout is working as expected, using the
supported clockid options.

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

selftests: futex: Expand timeout test

2021-05-12T18:44:59+00:00

Improve futex timeout testing by checking all the operations that
supports timeout and their available modes.

Signed-off-by: André Almeida 
Signed-off-by: Ingo Molnar 
Link: https://lore.kernel.org/r/20210427135328.11013-3-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: Add test plan API to kselftest.h and adjust callers

2019-04-25T19:15:46+00:00

The test plan for TAP needs to be declared immediately after the header.
This adds the test plan API to kselftest.h and updates all callers to
declare their expected test counts.

Signed-off-by: Kees Cook 
Signed-off-by: Shuah Khan

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: Add futex functional tests

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

The futextest testsuite [1] provides functional, stress, and
performance tests for the various futex op codes. Those tests will be of
more use to futex developers if they are included with the kernel
source.

Copy the core infrastructure and the functional tests into selftests,
but adapt them for inclusion in the kernel:

- Update the Makefile to include the run_tests target, remove reference
  to the performance and stress tests from the contributed sources.
- Replace my dead IBM email address with my current Intel email address.
- Remove the warrantee and write-to paragraphs from the license blurbs.
- Remove the NAME section as the filename is easily determined. ;-)
- Make the whitespace usage consistent in a couple of places.
- Cleanup various CodingStyle violations.

A future effort will explore moving the performance and stress tests
into the kernel.

1. http://git.kernel.org/cgit/linux/kernel/git/dvhart/futextest.git

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