diff options
| author | James Smart <jsmart2021@gmail.com> | 2019-08-15 02:56:50 +0300 |
|---|---|---|
| committer | Martin K. Petersen <martin.petersen@oracle.com> | 2019-08-20 05:41:10 +0300 |
| commit | a6d10f24a04d658078582fc0a89b20f050c0ae68 (patch) | |
| tree | 8b9455a8a145bc3f66e73c7be4808740fd9c4f78 /drivers/scsi/lpfc/lpfc_hbadisc.c | |
| parent | c26c265b168bb09013922846a51447603bcdfdc4 (diff) | |
| download | linux-a6d10f24a04d658078582fc0a89b20f050c0ae68.tar.xz | |
scsi: lpfc: Fix driver nvme rescan logging
In situations where zoning is not being used, thus NVMe initiators see
other NVMe initiators as well as NVMe targets, a link bounce on an
initiator will cause the NVMe initiators to spew "6169" State Error
messages.
The driver is not qualifying whether the remote port is a NVMe targer or
not before calling the lpfc_nvme_rescan_port(), which validates the role
and prints the message if its only an NVMe initiator.
Fix by the following:
- Before calling lpfc_nvme_rescan_port() ensure that the node is a NVMe
storage target or a NVMe discovery controller.
- Clean up implementation of lpfc_nvme_rescan_port. remoteport pointer
will always be NULL if a NVMe initiator only. But, grabbing of
remoteport pointer should be done under lock to coincide with the
registering of the remote port with the fc transport.
Signed-off-by: Dick Kennedy <dick.kennedy@broadcom.com>
Signed-off-by: James Smart <jsmart2021@gmail.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'drivers/scsi/lpfc/lpfc_hbadisc.c')
0 files changed, 0 insertions, 0 deletions