Re: [PATCH v3 3/3] test-ww_mutex: Handle transient -EDEADLK in test_cycle_work

> On 4 Aug 2026, at 18:31, Håkon Bugge <[email protected]> wrote:
> 
> There is a timing issue in test_cycle_work(), in the sense that
> acquiring *a_mutex* after deadlock has been detected on the *b_mutex*,
> may not succeed immediately. This may lead to false negatives, which
> shows up in the log as:
> 
>   cyclic deadlock not resolved, ret[77/93] = -35
> 
> We re-factor the inner part test_cycle_work(), where we loop a few
> times attempting to acquire the mutexes in BAAB order. If the first A
> succeeds or the last B succeeds, we break out of the loop.
> 
> Fixes: d1b42b800e5d ("locking/ww_mutex: Add kselftests for resolving ww_mutex cyclic deadlocks")
> Fixes: e4a02ed2aaf4 ("locking/ww_mutex: Fix runtime warning in the WW mutex selftest")
> Signed-off-by: Håkon Bugge <[email protected]>
> Acked-by: John Stultz <[email protected]>

A gentle ping on the v3 of this series.


Thxs, Håkon