First, avoid double request completion for nvmf_fail_nonready_command if
the request is freed asynchronously.
Second, avoid IO error. If work with nvme native multipath, rdma HBA
drivers may failed due to failed hardware, queue_rq should failed the
request instead of returning error to block layer, So upper layer can
failover the request if another path is available.
Need set the state of request to MQ_RQ_COMPLETE when queue_rq directly
complete the request. So introduce blk_mq_set_request_complete.
V5:
- add comment for blk_mq_set_request_complete.
- fail the request just for -EIO returned by rdma HBA drivers.
- delete the helper: nvme_complete_failed_req.
V4:
- add status parameter for nvme_complete_failed_req.
- export nvme_complete_failed_req instead of inline function.
V3:
- complete the request just for HBA driver path related error.
V2:
- use "switch" instead "if" to check return status.
Chao Leng (3):
blk-mq: introduce blk_mq_set_request_complete
nvme-fabrics: avoid double request completion for
nvmf_fail_nonready_command
nvme-rdma: avoid IO error for nvme native multipath
drivers/nvme/host/fabrics.c | 2 +-
drivers/nvme/host/rdma.c | 13 ++++++++++++-
include/linux/blk-mq.h | 9 +++++++++
3 files changed, 22 insertions(+), 2 deletions(-)
--
2.16.4
