Hi, a question about qla2xxx lock ordering since it trips up with Ingo's lock depenceny tool: in qla2x00_mailbox_command() the code first grabs the mbx_reg_lock lock, then the hardware_lock. So far so good. But then... it drops the mbx_reg_lock, does stuff, and regrabs the mbx_reg_lock lock, while keeping the hardware_lock held! This appears to be an AB-BA deadlock risk since for the second part you are taking the locks in the wrong order... or am I missing something here? Greetings, Arjan van de Ven - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
