[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180403144300.GE4082@hirez.programming.kicks-ass.net>
Date: Tue, 3 Apr 2018 16:43:00 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: David Howells <dhowells@...hat.com>,
Andrea Parri <andrea.parri@...rulasolutions.com>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
Andrea Parri <parri.andrea@...il.com>,
Alan Stern <stern@...land.harvard.edu>,
Will Deacon <will.deacon@....com>,
Boqun Feng <boqun.feng@...il.com>,
Nicholas Piggin <npiggin@...il.com>,
Jade Alglave <j.alglave@....ac.uk>,
Luc Maranget <luc.maranget@...ia.fr>,
Akira Yokosawa <akiyks@...il.com>
Subject: Re: [PATCH v2 1/3] locking: Document the semantics of
spin_is_locked()
On Tue, Apr 03, 2018 at 07:17:18AM -0700, Paul E. McKenney wrote:
> Suggestions for a fix? Clearly great care is required when using it
> in things like WARN_ON()...
Yeah, don't use it there, use lockdep_assert_held().
As I stated before in this thread, ideally we'd make *_is_locked() go
away entirely.
Powered by blists - more mailing lists