diff options
| author | Nysal Jan K.A <nysal@linux.ibm.com> | 2023-08-14 13:39:27 +0530 |
|---|---|---|
| committer | Shuah Khan <skhan@linuxfoundation.org> | 2023-08-16 10:48:10 -0600 |
| commit | fbf4dec702774286db409815ffb077711a96b824 (patch) | |
| tree | 646f1ef06fcacb83b22e1c57d0ba9238e9bbcc51 /scripts/generate_rust_analyzer.py | |
| parent | 888c72d581983ba935d73daed90a7ae4838fc6e1 (diff) | |
selftests/futex: Order calls to futex_lock_pi
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 <nysal@linux.ibm.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions