> With 2.6.31-rc9 + patch 4e49627b9bc29a14b393c480e8c979e3bc922ef7 + the
> patch you posted at the start of this thread the following lockdep
> complaint was triggered on the SRP initiator system during SRP login:
>
> ======================================================
> [ INFO: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected ]
> 2.6.31-rc9 #2
> ------------------------------------------------------
> ibsrpdm/4290 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
> (&(&rmpp_recv->cleanup_work)->timer){+.-...}, at:
> [<ffffffff802559f0>] del_timer_sync+0x0/0xa0
>
> and this task is already holding:
> (&mad_agent_priv->lock){..-...}, at: [<ffffffffa03c6de8>]
> ib_cancel_rmpp_recvs+0x28/0x118 [ib_mad]
> which would create a new lock dependency:
> (&mad_agent_priv->lock){..-...} ->
> (&(&rmpp_recv->cleanup_work)->timer){+.-...}
And this report doesn't happen with the older patch? (Did you do the
same testing with the older patch that triggered this)
Because this looks like a *different* incarnation of the same
lock->lock->delayed work/timer that we're trying to fix here -- the
delayed work is now rmpp_recv->cleanup_work in this case instead of
mad_agent_priv->timed_work as it was before.
- R.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
