scsi: libfc: Do not take rdata->rp_mutex when processing a -FC_EX_CLOSED ELS response.
When an ELS response handler receives a -FC_EX_CLOSED, the rdata->rp_mutex is
already held which can lead to a deadlock condition like the following stack trace:
[<
ffffffffa04d8f18>] fc_rport_plogi_resp+0x28/0x200 [libfc]
[<
ffffffffa04cfa1a>] fc_invoke_resp+0x6a/0xe0 [libfc]
[<
ffffffffa04d0c08>] fc_exch_mgr_reset+0x1b8/0x280 [libfc]
[<
ffffffffa04d87b3>] fc_rport_logoff+0x43/0xd0 [libfc]
[<
ffffffffa04ce73d>] fc_disc_stop+0x6d/0xf0 [libfc]
[<
ffffffffa04ce7ce>] fc_disc_stop_final+0xe/0x20 [libfc]
[<
ffffffffa04d55f7>] fc_fabric_logoff+0x17/0x70 [libfc]
The other ELS handlers need to follow the FLOGI response handler and simply do
a kref_put against the fc_rport_priv struct and exit when receving a
-FC_EX_CLOSED response.
Signed-off-by: Chad Dupuis <chad.dupuis@cavium.com>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Acked-by: Johannes Thumshirn <jth@kernel.org>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>