[ofa-general] Re: 2.6.30.1: possible irq lock inversion dependency detected

[Sean Hefty]

>And that will deadlock waiting in del_timer_sync() since the timer has
>been interrupted by an interrupt handler that will spin on a spinlock
>that is part of this chain.
>
>I'm not sure what the right fix is.  It does seem to me that this should
>be fixed within the ib_mad module, since doing del_timer_sync() within a
>spinlocked region seems like the fundamental problem.  However I'm not
>sure what the best way to rewrite the ib_mad usage is.

If I followed this correctly, will moving calls to cancel_delayed_work() outside
of any spinlocks fix this?  (If so, it's not immediately obvious to me what the
best fix is either.)

- Sean