[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210316153119.13802-1-longman@redhat.com>
Date: Tue, 16 Mar 2021 11:31:15 -0400
From: Waiman Long <longman@...hat.com>
To: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, Will Deacon <will@...nel.org>,
Boqun Feng <boqun.feng@...il.com>,
"Paul E. McKenney" <paulmck@...nel.org>,
Davidlohr Bueso <dave@...olabs.net>
Cc: linux-kernel@...r.kernel.org, Juri Lelli <juri.lelli@...hat.com>,
Waiman Long <longman@...hat.com>
Subject: [PATCH 0/4] locking/ww_mutex: Fix locktorture ww_mutex test problems
It was found that lockdep splat was produced whenever the ww_mutex
locktorture test was run on a kernel with lockdep enabled. It turns out
that there are bugs both in the ww_mutex and the locktorture code. This
patch series fix these bugs so that the ww_mutex locktorture test is
able to run without producing unexpected lockdep splat.
Patches 1 & 2 are clean-up patches for ww_mutex. Patch 3 fixes the lockdep
bug in ww_mutex and patch 4 fixes a bug in the locktorture code.
Waiman Long (4):
locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling
locking/ww_mutex: Fix acquire/release imbalance in
ww_acquire_init()/ww_acquire_fini()
locking/ww_mutex: Treat ww_mutex_lock() like a trylock
locking/locktorture: Fix incorrect use of ww_acquire_ctx in ww_mutex
test
include/linux/ww_mutex.h | 5 ++-
kernel/locking/locktorture.c | 86 +++++++++++++++++++++++-------------
kernel/locking/mutex.c | 30 ++++++++-----
3 files changed, 77 insertions(+), 44 deletions(-)
--
2.18.1
Powered by blists - more mailing lists