[ofw] deadlock starting in __free_mads

Hefty, Sean sean.hefty at intel.com
Mon Jan 3 08:43:46 PST 2011


> I have reached a deadlock caused by the fact that the function __free_mads
> takes h_al->mad_lock
> 
> It then calls ib_put_mad which calls al_remove_mad that will try to take
> the same lock.

How did this not blow up 4 years ago?




More information about the ofw mailing list