[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230509193039.GB2148518@hirez.programming.kicks-ass.net>
Date: Tue, 9 May 2023 21:30:39 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Kent Overstreet <kent.overstreet@...ux.dev>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-bcachefs@...r.kernel.org,
Kent Overstreet <kent.overstreet@...il.com>,
Ingo Molnar <mingo@...hat.com>, Will Deacon <will@...nel.org>,
Waiman Long <longman@...hat.com>,
Boqun Feng <boqun.feng@...il.com>
Subject: Re: [PATCH 02/32] locking/lockdep: lock_class_is_held()
On Tue, May 09, 2023 at 12:56:27PM -0400, Kent Overstreet wrote:
> From: Kent Overstreet <kent.overstreet@...il.com>
>
> This patch adds lock_class_is_held(), which can be used to assert that a
> particular type of lock is not held.
How is lock_is_held_type() not sufficient? Which is what's used to
implement lockdep_assert_held*().
Powered by blists - more mailing lists