scsi: storvsc: Fix scsi_cmd error assignments in storvsc_handle_error

When an I/O is returned with an srb_status of SRB_STATUS_INVALID_LUN
which has zero good_bytes it must be assigned an error. Otherwise the
I/O will be continuously requeued and will cause a deadlock in the case
where disks are being hot added and removed. sd_probe_async will wait
forever for its I/O to complete while holding scsi_sd_probe_domain.

Also returning the default error of DID_TARGET_FAILURE causes multipath
to not retry the I/O resulting in applications receiving I/O errors
before a failover can occur.

Signed-off-by: Cathy Avery <cavery@redhat.com>
Signed-off-by: Long Li <longli@microsoft.com>
Reviewed-by: Stephen Hemminger <stephen@networkplumber.org>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

authored by Cathy Avery and committed by Martin K. Petersen d1b8b239 81b6c999

+2 -1
+2 -1
drivers/scsi/storvsc_drv.c
··· 953 case TEST_UNIT_READY: 954 break; 955 default: 956 - set_host_byte(scmnd, DID_TARGET_FAILURE); 957 } 958 break; 959 case SRB_STATUS_INVALID_LUN: 960 do_work = true; 961 process_err_fn = storvsc_remove_lun; 962 break;
··· 953 case TEST_UNIT_READY: 954 break; 955 default: 956 + set_host_byte(scmnd, DID_ERROR); 957 } 958 break; 959 case SRB_STATUS_INVALID_LUN: 960 + set_host_byte(scmnd, DID_NO_CONNECT); 961 do_work = true; 962 process_err_fn = storvsc_remove_lun; 963 break;