From: "Håkon Bugge" <haakon.bugge@oracle.com>
To: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Boqun Feng <boqun@kernel.org>, Waiman Long <longman@redhat.com>,
John Stultz <jstultz@google.com>
Cc: "Håkon Bugge" <haakon.bugge@oracle.com>,
"Ingo Molnar" <mingo@kernel.org>
Subject: [PATCH 4/4] test-ww_mutex: Retry lock acquisition after timeout if deadlocked
Date: Wed, 17 Jun 2026 14:13:33 +0200 [thread overview]
Message-ID: <20260617121335.2036954-5-haakon.bugge@oracle.com> (raw)
In-Reply-To: <20260617121335.2036954-1-haakon.bugge@oracle.com>
stress_inorder_work() terminates when its timeout expires. If the
final lock acquisition attempt returns -EDEADLK at that point, the
test may report a false failure even though the deadlock would have
been resolved shortly thereafter. Retry a limited number of times
after timeout before reporting failure.
Without this commit, we may see in the log:
Beginning ww (wound) mutex selftests
stress (stress_inorder_work) failed with -35
Fixes: cfa92b6d5207 ("locking/ww_mutex/test: Make sure we bail out instead of livelock")
Signed-off-by: Håkon Bugge <haakon.bugge@oracle.com>
---
kernel/locking/test-ww_mutex.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/kernel/locking/test-ww_mutex.c b/kernel/locking/test-ww_mutex.c
index 6b29a7a8f5fba..95de03179eac0 100644
--- a/kernel/locking/test-ww_mutex.c
+++ b/kernel/locking/test-ww_mutex.c
@@ -444,6 +444,7 @@ static void stress_inorder_work(struct work_struct *work)
struct ww_acquire_ctx ctx;
int *order;
int err;
+ int attempts_after_tmout = 10000;
stress->result = -ENOMEM;
@@ -476,7 +477,7 @@ static void stress_inorder_work(struct work_struct *work)
ww_mutex_unlock(&locks[order[n]]);
if (err == -EDEADLK) {
- if (!time_after(jiffies, stress->timeout)) {
+ if ((!time_after(jiffies, stress->timeout)) || attempts_after_tmout--) {
ww_mutex_lock_slow(&locks[order[contended]], &ctx);
goto retry;
}
--
2.43.5
next prev parent reply other threads:[~2026-06-17 12:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 12:13 [PATCH 0/4] test-ww_mutex: Miscellaneous fixes Håkon Bugge
2026-06-17 12:13 ` [PATCH 1/4] test-ww_mutex: Fix module cleanup Håkon Bugge
2026-06-18 17:49 ` John Stultz
2026-06-17 12:13 ` [PATCH 2/4] test-ww_mutex: Report errors from stress workers Håkon Bugge
2026-06-18 17:52 ` John Stultz
2026-07-09 0:03 ` John Stultz
2026-07-09 16:51 ` Haakon Bugge
2026-06-17 12:13 ` [PATCH 3/4] test-ww_mutex: Handle transient -EDEADLK in test_cycle_work Håkon Bugge
2026-06-18 19:04 ` John Stultz
2026-06-22 13:21 ` Haakon Bugge
2026-07-08 19:55 ` John Stultz
2026-07-09 17:05 ` Haakon Bugge
2026-06-17 12:13 ` Håkon Bugge [this message]
2026-06-18 18:55 ` [PATCH 4/4] test-ww_mutex: Retry lock acquisition after timeout if deadlocked John Stultz
2026-06-22 13:47 ` Haakon Bugge
2026-07-06 9:01 ` Haakon Bugge
2026-07-06 9:02 ` Haakon Bugge
2026-07-08 20:01 ` John Stultz
2026-07-09 16:56 ` Haakon Bugge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260617121335.2036954-5-haakon.bugge@oracle.com \
--to=haakon.bugge@oracle.com \
--cc=boqun@kernel.org \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®