[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YCljfeNr4m5mZa4N@hirez.programming.kicks-ass.net>
Date: Sun, 14 Feb 2021 18:53:01 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Shuah Khan <skhan@...uxfoundation.org>
Cc: mingo@...hat.com, will@...nel.org, kvalo@...eaurora.org,
davem@...emloft.net, kuba@...nel.org, ath10k@...ts.infradead.org,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] lockdep: add lockdep_assert_not_held()
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.
Powered by blists - more mailing lists