Hi all,
I'm seeing a mutex recursion in
fc_lport_reset -> fc_exch_mgr_reset -> fc_lport_flogi_resp -> mutex_lock
Since fc_lport_reset already holds the lock, this is a problem. I suspect
that's
true of other response handlers.
Perhaps the exch_mgr_reset should do the response callbacks from a
scheduled work routine or something.
Another idea: call exch_mgr_reset() before grabbing the lock in
fc_lport_reset().
Have exch_mgr_reset() set some flag that keeps the exch_mgr from allowing new
exchanges to be started until that flag gets cleared. Then after the lport
is locked and the state changed, call something that resets that flag.
Other ideas?
Joe
_______________________________________________
devel mailing list
[email protected]
http://www.open-fcoe.org/mailman/listinfo/devel
