diff options
| author | James Smart <jsmart2021@gmail.com> | 2018-04-09 14:24:29 -0700 |
|---|---|---|
| committer | Martin K. Petersen <martin.petersen@oracle.com> | 2018-04-18 19:34:05 -0400 |
| commit | b04744ce52a8da883c8b87b66082f9805bb4ca32 (patch) | |
| tree | d1515b764179a045240bb55a7083199cc92f0b04 /tools/perf/scripts/python/call-graph-from-sql.py | |
| parent | bf316c78517d9437656293f65a70d6ecdc2ec58e (diff) | |
| download | linux-b04744ce52a8da883c8b87b66082f9805bb4ca32.tar.gz linux-b04744ce52a8da883c8b87b66082f9805bb4ca32.zip | |
scsi: lpfc: Fix driver not recovering NVME rports during target link faults
During target-side port faults, the driver would not recover all target
port logins. This resulted in a loss of nvme device discovery.
The driver is coded to wait for all GID_FT requests to complete before
restarting discovery. A fault is seen where the outstanding GIT_FT
counts are not properly decremented, thus discovery would never
start. Another fault was found in the clearing of the gidft_inp counter
that would be skipped in this condition. And a third fault found with
lpfc_nvme_register_port that would remove a reverence on the ndlp which
then allows a node swap on a port address change to prematurely remove
the reference and release the ndlp.
The following changes are made:
- Correct the decrementing of the outstanding GID_FT counters.
- In RSCN handling, no longer zero the counter before calling to issue
another GID_FT.
- No longer remove the reference on the dlp when the ndlp->nrport value
is not yet null.
Signed-off-by: Dick Kennedy <dick.kennedy@broadcom.com>
Signed-off-by: James Smart <james.smart@broadcom.com>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-sql.py')
0 files changed, 0 insertions, 0 deletions