diff options
| author |   Mike Christie <michael.christie@oracle.com> | 2022-08-11 20:00:20 -0500 |
|---|---|---|
| committer |   Martin K. Petersen <martin.petersen@oracle.com> | 2022-09-06 22:05:58 -0400 |
| commit | f1d0d5c9fe37d45e5f3004e54a4e596220bae930 (patch) | |
| tree | d9171d866329b1848e4d8d1082b6537630223ce3 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | scsi: storvsc: Drop DID_TARGET_FAILURE use (diff) | |
| download | linux-dev-f1d0d5c9fe37d45e5f3004e54a4e596220bae930.tar.xz linux-dev-f1d0d5c9fe37d45e5f3004e54a4e596220bae930.zip | |
scsi: uas: 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.
It looks like the driver wanted a hard failure so this swaps it with
DID_BAD_TARGET which gives us that behavior. The error looks like it's for
a case where the target did not support a TMF we wanted to use (maybe not a
bad target but disappointing so close enough).
Link: https://lore.kernel.org/r/20220812010027.8251-4-michael.christie@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