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.dup...@cavium.com>
---
 drivers/scsi/libfc/fc_rport.c | 32 ++++++++++++++++++++++++--------
 1 file changed, 24 insertions(+), 8 deletions(-)

diff --git a/drivers/scsi/libfc/fc_rport.c b/drivers/scsi/libfc/fc_rport.c
index 93f5961..6f19c12 100644
--- a/drivers/scsi/libfc/fc_rport.c
+++ b/drivers/scsi/libfc/fc_rport.c
@@ -884,10 +884,13 @@ static void fc_rport_plogi_resp(struct fc_seq *sp, struct 
fc_frame *fp,
        u16 cssp_seq;
        u8 op;
 
-       mutex_lock(&rdata->rp_mutex);
-
        FC_RPORT_DBG(rdata, "Received a PLOGI %s\n", fc_els_resp_type(fp));
 
+       if (fp == ERR_PTR(-FC_EX_CLOSED))
+               goto put;
+
+       mutex_lock(&rdata->rp_mutex);
+
        if (rdata->rp_state != RPORT_ST_PLOGI) {
                FC_RPORT_DBG(rdata, "Received a PLOGI response, but in state "
                             "%s\n", fc_rport_state(rdata));
@@ -926,6 +929,7 @@ out:
        fc_frame_free(fp);
 err:
        mutex_unlock(&rdata->rp_mutex);
+put:
        kref_put(&rdata->kref, lport->tt.rport_destroy);
 }
 
@@ -1008,10 +1012,13 @@ static void fc_rport_prli_resp(struct fc_seq *sp, 
struct fc_frame *fp,
        u8 op;
        u8 resp_code = 0;
 
-       mutex_lock(&rdata->rp_mutex);
-
        FC_RPORT_DBG(rdata, "Received a PRLI %s\n", fc_els_resp_type(fp));
 
+       if (fp == ERR_PTR(-FC_EX_CLOSED))
+               goto put;
+
+       mutex_lock(&rdata->rp_mutex);
+
        if (rdata->rp_state != RPORT_ST_PRLI) {
                FC_RPORT_DBG(rdata, "Received a PRLI response, but in state "
                             "%s\n", fc_rport_state(rdata));
@@ -1079,6 +1086,7 @@ out:
        fc_frame_free(fp);
 err:
        mutex_unlock(&rdata->rp_mutex);
+put:
        kref_put(&rdata->kref, rdata->local_port->tt.rport_destroy);
 }
 
@@ -1156,10 +1164,13 @@ static void fc_rport_rtv_resp(struct fc_seq *sp, struct 
fc_frame *fp,
        struct fc_rport_priv *rdata = rdata_arg;
        u8 op;
 
-       mutex_lock(&rdata->rp_mutex);
-
        FC_RPORT_DBG(rdata, "Received a RTV %s\n", fc_els_resp_type(fp));
 
+       if (fp == ERR_PTR(-FC_EX_CLOSED))
+               goto put;
+
+       mutex_lock(&rdata->rp_mutex);
+
        if (rdata->rp_state != RPORT_ST_RTV) {
                FC_RPORT_DBG(rdata, "Received a RTV response, but in state "
                             "%s\n", fc_rport_state(rdata));
@@ -1201,6 +1212,7 @@ out:
        fc_frame_free(fp);
 err:
        mutex_unlock(&rdata->rp_mutex);
+put:
        kref_put(&rdata->kref, rdata->local_port->tt.rport_destroy);
 }
 
@@ -1292,10 +1304,13 @@ static void fc_rport_adisc_resp(struct fc_seq *sp, 
struct fc_frame *fp,
        struct fc_els_adisc *adisc;
        u8 op;
 
-       mutex_lock(&rdata->rp_mutex);
-
        FC_RPORT_DBG(rdata, "Received a ADISC response\n");
 
+       if (fp == ERR_PTR(-FC_EX_CLOSED))
+               goto put;
+
+       mutex_lock(&rdata->rp_mutex);
+
        if (rdata->rp_state != RPORT_ST_ADISC) {
                FC_RPORT_DBG(rdata, "Received a ADISC resp but in state %s\n",
                             fc_rport_state(rdata));
@@ -1330,6 +1345,7 @@ out:
        fc_frame_free(fp);
 err:
        mutex_unlock(&rdata->rp_mutex);
+put:
        kref_put(&rdata->kref, rdata->local_port->tt.rport_destroy);
 }
 
-- 
1.8.5.6

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to