Daniel Wagner ef2e3ec520 scsi: qla2xxx: Set NVMe status code for failed NVMe FCP request
The qla2xxx driver knows when request was processed successfully or
not. But it always sets the NVMe status code to 0/NVME_SC_SUCCESS. The
upper layer needs to figure out from the rcv_rsplen and transferred_length
variables if the request was transferred successfully. This is not always
possible, e.g. when the request data length is 0, the transferred_length is
also set 0 which is interpreted as success in nvme_fc_fcpio_done(). Let's
inform the upper layer (nvme_fc_fcpio_done()) when something went wrong.

nvme_fc_fcpio_done() maps all non-NVME_SC_SUCCESS status codes to
NVME_SC_HOST_PATH_ERROR. There isn't any benefit to map the QLA status code
to the NVMe status code. Therefore, use NVME_SC_INTERNAL to indicate an
error which aligns it with the lpfc driver.

Link: https://lore.kernel.org/r/20200604100745.89250-1-dwagner@suse.de
Reviewed-by: Himanshu Madhani <himanshu.madhani@oracle.com>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Daniel Wagner <dwagner@suse.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
2020-06-23 23:48:26 -04:00
..
2020-04-02 17:03:53 -07:00
2020-06-13 13:17:49 -07:00
2020-01-29 18:16:16 -08:00
2019-11-07 06:43:18 -07:00
2020-03-11 23:07:59 -04:00
2020-06-13 13:17:49 -07:00
2020-04-10 12:21:11 -07:00
2020-06-05 15:11:50 -07:00
2020-06-13 13:29:16 -07:00
2020-06-13 13:29:16 -07:00
2019-03-02 11:39:54 -08:00
2019-11-12 22:21:35 -05:00
2020-02-24 14:54:25 -05:00
2020-03-11 23:07:59 -04:00
2020-04-14 21:32:39 -04:00
2019-01-08 21:58:35 -05:00
2020-02-28 20:54:52 -05:00
2019-07-11 15:14:01 -07:00
2020-06-04 10:15:32 -04:00
2019-06-18 19:46:18 -04:00
2019-07-11 15:17:41 -07:00
2020-04-02 17:03:53 -07:00
2018-11-06 21:31:28 -05:00
2019-07-11 15:14:01 -07:00
2020-03-24 07:57:07 -06:00
2019-07-11 15:17:41 -07:00
2020-06-05 15:11:50 -07:00
2019-07-11 15:14:01 -07:00
2020-06-02 15:29:19 -07:00
2020-06-05 15:11:50 -07:00
2019-07-11 15:14:01 -07:00
2020-06-13 13:17:49 -07:00
2020-02-24 15:01:57 -05:00
2020-06-13 13:17:49 -07:00
2020-02-10 22:46:55 -05:00
2019-07-11 15:14:01 -07:00