Files
Martin Wilck ebfb07e8c2 scsi: core: reset host byte in DID_NEXUS_FAILURE case
commit 4a067cf823 upstream.

Up to 4.12, __scsi_error_from_host_byte() would reset the host byte to
DID_OK for various cases including DID_NEXUS_FAILURE.  Commit
2a842acab1 ("block: introduce new block status code type") replaced this
function with scsi_result_to_blk_status() and removed the host-byte
resetting code for the DID_NEXUS_FAILURE case.  As the line
set_host_byte(cmd, DID_OK) was preserved for the other cases, I suppose
this was an editing mistake.

The fact that the host byte remains set after 4.13 is causing problems with
the sg_persist tool, which now returns success rather then exit status 24
when a RESERVATION CONFLICT error is encountered.

Fixes: 2a842acab1 "block: introduce new block status code type"
Signed-off-by: Martin Wilck <mwilck@suse.com>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-03-10 07:17:21 +01:00
..
2019-02-12 19:47:25 +01:00
2018-06-19 22:02:25 -04:00
2018-07-10 22:42:47 -04:00
…
2018-06-12 16:19:22 -07:00
2018-08-21 23:54:17 -04:00
2018-06-12 16:19:22 -07:00
2017-12-04 20:32:53 -05:00
…
…
…
…
…
…
…
2018-06-19 22:02:25 -04:00
2018-06-19 22:02:25 -04:00
2018-06-19 22:02:25 -04:00
2018-06-12 16:19:22 -07:00
2018-05-18 12:03:51 -04:00
2018-06-19 22:02:25 -04:00
2018-06-19 22:02:25 -04:00
…
…
…
…
…
…
…
…
…
2018-06-12 16:19:22 -07:00
2018-06-12 16:19:22 -07:00
…
…
…
2018-06-19 22:02:25 -04:00
2018-06-12 16:19:22 -07:00
…
…
…
…
…
…
2018-05-01 23:30:12 -04:00
…