Re: [PATCH] lock assertion macros for 2.5.28

[Jesse Barnes <jbarnes@sgi.com>]

On Fri, Jul 26, 2002 at 06:54:16PM +0100, Christoph Hellwig wrote:
> On Fri, Jul 26, 2002 at 10:42:58AM -0700, Jesse Barnes wrote:
> > On Fri, Jul 26, 2002 at 04:09:18PM +0400, Joshua MacDonald wrote:
> > > In reiser4 we are looking forward to having a MUST_NOT_HOLD (i.e.,
> > > spin_is_not_locked) assertion for kernel spinlocks.  Do you know if any
> > > progress has been made in that direction?
> > 
> > Well, I had that in one version of the patch, but people didn't think
> > it would be useful.  Maybe you'd like to check out Oliver's comments
> > at http://marc.theaimsgroup.com/?l=linux-kernel&m=102644431806734&w=2
> > and respond?  If there's demand for MUST_NOT_HOLD, I'd be happy to add
> > it since it should be easy.  But if you're using it to enforce lock
> > ordering as Oliver suggests, then there are probably more robust
> > solutions.
> 
> Why don't you just generalize the scsi version that already support this?
> 
> reinventing the wheel everywhere..

Well, I wouldn't go that far.  The macros are really simple and
implementing a MUST_NOT_HOLD should be easy too.  It could also be
done in a much more useful way than how ASSERT_LOCK works, by tracking
where the locks where acquired for example.

Did you check out the thread above?  Having ASSERT_LOCK(&lock, 0)
doesn't seem that useful by itself.  A lot of the scsi code does
things like:

  ASSERT_LOCK(&lock, 0);
  ...
  spin_lock(&lock);

What does that buy you?  The suggestions for tracking where the lock
was acquired (in the thread above) seem much more useful.

Thanks,
Jesse