and somewhere else
spin_lock(b);
spin_lock(a);
>
> Run time checks for xxx_irq when irq is already off seem reasonable.
> The implication is that the xxx_unlockirq will then turn it on, which
> most likely is an error. Also, see above about rolling assumptions in
> to the macro name.
>
Unfortuantely there are still a few special cases where spin_lock_irq()
with already disabled interrupts is both intentional and correct^wnot
buggy (search for sleep_on and cli() through the lkml archives).
And there are optimizations such as
spin_lock_bh(a);
spin_unlock(b);
spin_lock(b);
spin_unlock_bh(b);
-- Manfred - 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/