diff options
| author |   Mike Christie <michael.christie@oracle.com> | 2022-08-11 20:00:23 -0500 |
|---|---|---|
| committer |   Martin K. Petersen <martin.petersen@oracle.com> | 2022-09-06 22:05:58 -0400 |
| commit | a965d35c8741724eb69050948024f35d268645ab (patch) | |
| tree | 2ef765f700c1831e4dd12fa62306725f50115fe1 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | scsi: virtio_scsi: Drop DID_NEXUS_FAILURE use (diff) | |
| download | linux-dev-a965d35c8741724eb69050948024f35d268645ab.tar.xz linux-dev-a965d35c8741724eb69050948024f35d268645ab.zip | |
scsi: qla2xxx: Drop DID_TARGET_FAILURE use
DID_TARGET_FAILURE is internal to the SCSI layer. Drivers must not use it
because:
1. It's not propagated upwards, so SG IO/passthrough users will not see an
error and think a command was successful.
2. There is no handling for it in scsi_decide_disposition() so it
results in entering SCSI error handling.
This has qla2xxx use DID_NO_CONNECT because it looks like we hit this error
when we can't find a port. It will give us the same hard error behavior and
it seems to match the error where we can't find the endpoint.
Link: https://lore.kernel.org/r/20220812010027.8251-7-michael.christie@oracle.com
Reviewed-by: Himanshu Madhani <himanshu.madhani@oracle.com>
Signed-off-by: Mike Christie <michael.christie@oracle.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions