Fixes for test-ww_mutex stress test
Status from this message: The following commit has been merged into the locking/core branch of tip:
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | test-ww_mutex: Use prng instead of rng to avoid hangs at bootupkernel/ | +17 | 0 replies | |
| 2/3 | test-ww_mutex: Fix potential workqueue corruptionkernel/ | +12 | 0 replies | |
| 3/3 | test-ww_mutex: Make sure we bail out instead of livelockkernel/ | +5 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] Fixes for test-ww_mutex stress test
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
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(-)
Signature · 1 line
2.42.0.515.g380fc7ccd1-goog