Some kernel functions must not be called holding a specific lock. Doing
so could lead to locking problems. Currently these routines call
lock_is_held() to check for lock hold followed by WARN_ON.
Adding a common lockdep interface will help reduce the duplication of this
logic in the rest of the kernel.
Add lockdep_assert_not_held() to be used in these functions to detect
incorrect calls while holding a lock.
lockdep_assert_not_held() provides the opposite functionality of
lockdep_assert_held() which is used to assert calls that require
holding a specific lock.
The need for lockdep_assert_not_held() came up in a discussion on
ath10k patch. ath10k_drain_tx() and i915_vma_pin_ww() are examples
of functions that can use lockdep_assert_not_held().
Link: https://lore.kernel.org/linux-wireless/871rdmu9z9.fsf@codeaurora.org/
This patch series adds lockdep_assert_not_held() and uses it in the
second patch in ath10k_drain_tx() function.
Shuah Khan (2):
lockdep: add lockdep_assert_not_held()
ath10k: detect conf_mutex held ath10k_drain_tx() calls
drivers/net/wireless/ath/ath10k/mac.c | 2 ++
include/linux/lockdep.h | 7 ++++++-
2 files changed, 8 insertions(+), 1 deletion(-)
--
2.27.0
Some kernel functions must not be called holding a specific lock. Doing
so could lead to locking problems. Currently these routines call
lock_is_held() to check for lock hold followed by WARN_ON.
Adding a common lockdep interface will help reduce the duplication of this
logic in the rest of the kernel.
Add lockdep_assert_not_held() to be used in these functions to detect
incorrect calls while holding a lock.
lockdep_assert_not_held() provides the opposite functionality of
lockdep_assert_held() which is used to assert calls that require
holding a specific lock.
The need for lockdep_assert_not_held() came up in a discussion on
ath10k patch. ath10k_drain_tx() and i915_vma_pin_ww() are examples
of functions that can use lockdep_assert_not_held().
Link: https://lore.kernel.org/linux-wireless/871rdmu9z9.fsf@codeaurora.org/
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
---
include/linux/lockdep.h | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
@@ -383,8 +387,9 @@ extern int lock_is_held(const void *);externintlockdep_is_held(constvoid*);#define lockdep_is_held_type(l, r) (1)+#define lockdep_assert_not_held(l) do { (void)(l); } while (0)#define lockdep_assert_held(l) do { (void)(l); } while (0)-#define lockdep_assert_held_write(l) do { (void)(l); } while (0)+#define lockdep_assert_held_write(l) do { (void)(l); } while (0)#define lockdep_assert_held_read(l) do { (void)(l); } while (0)#define lockdep_assert_held_once(l) do { (void)(l); } while (0)
ath10k_drain_tx() must not be called with conf_mutex held as workers can
use that also. Add call to lockdep_assert_not_held() on conf_mutex to
detect if conf_mutex is held by the caller.
The idea for this patch stemmed from coming across the comment block
above the ath10k_drain_tx() while reviewing the conf_mutex holds during
to debug the conf_mutex lock assert in ath10k_debug_fw_stats_request().
Adding detection to assert on conf_mutex hold will help detect incorrect
usages that could lead to locking problems when async worker routines try
to call this routine.
Link: https://lore.kernel.org/linux-wireless/871rdmu9z9.fsf@codeaurora.org/
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
---
drivers/net/wireless/ath/ath10k/mac.c | 2 ++
1 file changed, 2 insertions(+)
@@ -4728,6 +4728,8 @@ static void ath10k_mac_op_wake_tx_queue(struct ieee80211_hw *hw,/* Must not be called with conf_mutex held as workers can use that also. */voidath10k_drain_tx(structath10k*ar){+lockdep_assert_not_held(&ar->conf_mutex);+/* make sure rcu-protected mac80211 tx path itself is drained */synchronize_net();
From: Peter Zijlstra <peterz@infradead.org> Date: 2021-02-14 17:53:59
On Fri, Feb 12, 2021 at 04:28:42PM -0700, Shuah Khan wrote:
+#define lockdep_assert_not_held(l) do { \
+ WARN_ON(debug_locks && lockdep_is_held(l)); \
+ } while (0)
+
This thing isn't as straight forward as you might think, but it'll
mostly work.
Notably this thing will misfire when lockdep_off() is employed. It
certainyl needs a comment to explain the subtleties.
From: Peter Zijlstra <peterz@infradead.org> Date: 2021-02-15 10:51:45
On Sun, Feb 14, 2021 at 06:53:01PM +0100, Peter Zijlstra wrote:
On Fri, Feb 12, 2021 at 04:28:42PM -0700, Shuah Khan wrote:
quoted
+#define lockdep_assert_not_held(l) do { \
+ WARN_ON(debug_locks && lockdep_is_held(l)); \
+ } while (0)
+
This thing isn't as straight forward as you might think, but it'll
mostly work.
Notably this thing will misfire when lockdep_off() is employed. It
certainyl needs a comment to explain the subtleties.
I think something like so will work, but please double check.