diff options
| author | James Smart | 2018-10-23 22:41:08 +0200 |
|---|---|---|
| committer | Martin K. Petersen | 2018-11-07 02:42:51 +0100 |
| commit | d496b9a7246cb9813da1fe49e14edbbbf8e232d5 (patch) | |
| tree | 93018dd46acf569a824b46346009428d0c8f4254 /drivers/scsi/lpfc/lpfc.h | |
| parent | scsi: lpfc: Correct LCB RJT handling (diff) | |
| download | kernel-qcow2-linux-d496b9a7246cb9813da1fe49e14edbbbf8e232d5.tar.gz kernel-qcow2-linux-d496b9a7246cb9813da1fe49e14edbbbf8e232d5.tar.xz kernel-qcow2-linux-d496b9a7246cb9813da1fe49e14edbbbf8e232d5.zip | |
scsi: lpfc: Fix odd recovery in duplicate FLOGIs in point-to-point
Testing a point-to-point topology and a case of re-FLOGI without
intervening link bouncing, showed an odd interaction with firmware and
a resulting scenario where the driver no longer probed after accepting
the new FLOGI.
Work around the firmware issue by issuing a link bounce if a FLOGI is
received after the link is already up and FLOGI's accepted.
While debugging the issue, realized that some debug traces should be
clarified to help in the future.
Signed-off-by: Dick Kennedy <dick.kennedy@broadcom.com>
Signed-off-by: James Smart <jsmart2021@gmail.com>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'drivers/scsi/lpfc/lpfc.h')
| -rw-r--r-- | drivers/scsi/lpfc/lpfc.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/scsi/lpfc/lpfc.h b/drivers/scsi/lpfc/lpfc.h index c1eb2b00ca7f..95f0cdbb16a6 100644 --- a/drivers/scsi/lpfc/lpfc.h +++ b/drivers/scsi/lpfc/lpfc.h @@ -490,6 +490,7 @@ struct lpfc_vport { struct nvme_fc_local_port *localport; uint8_t nvmei_support; /* driver supports NVME Initiator */ uint32_t last_fcp_wqidx; + uint32_t rcv_flogi_cnt; /* How many unsol FLOGIs ACK'd. */ }; struct hbq_s { |