[ofa-general] Re: having problems with the latest for-2.6.27 tree

[Roland Dreier]

 > 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.