> With lock dep stuff on:
yep, the mutex_lock for conn_id in iw_conn_req_handler should really be
mutex_lock_nested(&conn_id->handler_mutex, SINGLE_DEPTH_NESTING);
since it's already inside another lock of the same class. but I don't
understand why it leads to a real deadlock... they're different mutexes
and I don't see how the conn_id lock could already be locked??
- R.
_______________________________________________
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
