On Tue, Sep 8, 2009 at 6:21 AM, Roland Dreier<[email protected]> wrote: > > > 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.
The above issue does not occur with the for-next branch of the infiniband git tree, but does occur with 2.6.31-rc9 + aforementioned patches. As far as I can see commit 721d67cdca5b7642b380ca0584de8dceecf6102f (http://git.kernel.org/?p=linux/kernel/git/roland/infiniband.git;a=commitdiff;h=721d67cdca5b7642b380ca0584de8dceecf6102f) is not yet included in 2.6.31-rc9. Could this be related to the above issue ? Bart. _______________________________________________ general mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
