From: John Stultz <jstultz@google.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: John Stultz <jstultz@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
"Paul E . McKenney" <paulmck@kernel.org>,
Joel Fernandes <joelaf@google.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
kernel-team@android.com
Subject: [PATCH 0/3] Fixes for test-ww_mutex stress test
Date: Fri, 22 Sep 2023 04:35:58 +0000 [thread overview]
Message-ID: <20230922043616.19282-1-jstultz@google.com> (raw)
As part of recent stabilizing of the proxy-execution series,
I've seen a number of issues from the test-ww_mutex module.
This test is great for shaking out problems in the patches, but
in some cases it seems the patch series has made it easier to
uncover problems in the test-ww_mutex stress tests.
So this patch series provides a few fixes that I've come up with
in testing with qemu using large cpu counts.
Feedback would be greatly appreciated!
thanks
-john
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Will Deacon <will@kernel.org>
Cc: Waiman Long <longman@redhat.com>
Cc: Boqun Feng <boqun.feng@gmail.com>
Cc: "Paul E . McKenney" <paulmck@kernel.org>
Cc: Joel Fernandes <joelaf@google.com>
Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>
Cc: kernel-team@android.com
John Stultz (3):
test-ww_mutex: Use prng instead of rng to avoid hangs at bootup
test-ww_mutex: Fix potential workqueue corruption
test-ww_mutex: Make sure we bail out instead of livelock
kernel/locking/test-ww_mutex.c | 48 ++++++++++++++++++++++++----------
1 file changed, 34 insertions(+), 14 deletions(-)
--
2.42.0.515.g380fc7ccd1-goog
next reply other threads:[~2023-09-22 4:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 4:35 John Stultz [this message]
2023-09-22 4:35 ` [PATCH 1/3] test-ww_mutex: Use prng instead of rng to avoid hangs at bootup John Stultz
2023-09-22 8:11 ` [tip: locking/core] locking/ww_mutex/test: " tip-bot2 for John Stultz
2023-09-22 4:36 ` [PATCH 2/3] test-ww_mutex: Fix potential workqueue corruption John Stultz
2023-09-22 8:11 ` [tip: locking/core] locking/ww_mutex/test: " tip-bot2 for John Stultz
2023-09-22 4:36 ` [PATCH 3/3] test-ww_mutex: Make sure we bail out instead of livelock John Stultz
2023-09-22 8:11 ` [tip: locking/core] locking/ww_mutex/test: " tip-bot2 for John Stultz
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=20230922043616.19282-1-jstultz@google.com \
--to=jstultz@google.com \
--cc=boqun.feng@gmail.com \
--cc=dietmar.eggemann@arm.com \
--cc=joelaf@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.