> > For MUST_NOT_HOLD to work, you need to take into account which processor
> > took the lock etc.
[snip]
> Agreed. I'll post another patch that doesn't mess with the scsi
> stuff. Maybe later I can put together a useful
> 'lock-not-held-on-this-cpu' macro.
You don't need to put this in a macro. This test is valid
for ALL spinlocks in the kernel and can be done from inside
the spin_lock() macro itself, when spinlock debugging is on.
regards,
Rik
-- http://www.linuxsymposium.org/2002/ "You're one of those condescending OLS attendants" "Here's a nickle kid. Go buy yourself a real t-shirt"http://www.surriel.com/ http://distro.conectiva.com/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/