On Tue, Apr 03, 2018 at 04:43:00PM +0200, Peter Zijlstra wrote:
> 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().
Good point, -ETOOEARLY. ;-)
> As I stated before in this thread, ideally we'd make *_is_locked() go
> away entirely.
After being reminded of the issues on UP systems, I now have much more
sympathy for that view...
Thanx, Paul
