From: Chao Leng <lengchao@huawei.com> To: <linux-nvme@lists.infradead.org> Cc: <kbusch@kernel.org>, <axboe@fb.com>, <hch@lst.de>, <sagi@grimberg.me>, <linux-block@vger.kernel.org>, <axboe@kernel.dk> Subject: [PATCH v3 0/5] avoid double request completion and IO error Date: Thu, 21 Jan 2021 15:03:25 +0800 [thread overview] Message-ID: <20210121070330.19701-1-lengchao@huawei.com> (raw) Add blk_mq_set_request_complete and nvme_complete_failed_req for two bug fixs. First avoid double request completion for nvmf_fail_nonready_command. Second avoid IO error for nvme native multipath. V3: - complete the request just for HBA driver path related error. V2: - use "switch" instead "if" to check return status. Chao Leng (5): blk-mq: introduce blk_mq_set_request_complete nvme-core: introduce complete failed request nvme-fabrics: avoid double request completion for nvmf_fail_nonready_command nvme-rdma: avoid IO error for nvme native multipath nvme-fc: avoid IO error for nvme native multipath drivers/nvme/host/fabrics.c | 4 +--- drivers/nvme/host/fc.c | 7 ++++++- drivers/nvme/host/nvme.h | 8 ++++++++ drivers/nvme/host/rdma.c | 9 ++++++++- include/linux/blk-mq.h | 5 +++++ 5 files changed, 28 insertions(+), 5 deletions(-) -- 2.16.4
WARNING: multiple messages have this Message-ID (diff)
From: Chao Leng <lengchao@huawei.com> To: <linux-nvme@lists.infradead.org> Cc: axboe@kernel.dk, linux-block@vger.kernel.org, sagi@grimberg.me, axboe@fb.com, kbusch@kernel.org, hch@lst.de Subject: [PATCH v3 0/5] avoid double request completion and IO error Date: Thu, 21 Jan 2021 15:03:25 +0800 [thread overview] Message-ID: <20210121070330.19701-1-lengchao@huawei.com> (raw) Add blk_mq_set_request_complete and nvme_complete_failed_req for two bug fixs. First avoid double request completion for nvmf_fail_nonready_command. Second avoid IO error for nvme native multipath. V3: - complete the request just for HBA driver path related error. V2: - use "switch" instead "if" to check return status. Chao Leng (5): blk-mq: introduce blk_mq_set_request_complete nvme-core: introduce complete failed request nvme-fabrics: avoid double request completion for nvmf_fail_nonready_command nvme-rdma: avoid IO error for nvme native multipath nvme-fc: avoid IO error for nvme native multipath drivers/nvme/host/fabrics.c | 4 +--- drivers/nvme/host/fc.c | 7 ++++++- drivers/nvme/host/nvme.h | 8 ++++++++ drivers/nvme/host/rdma.c | 9 ++++++++- include/linux/blk-mq.h | 5 +++++ 5 files changed, 28 insertions(+), 5 deletions(-) -- 2.16.4 _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-01-21 7:05 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-21 7:03 Chao Leng [this message] 2021-01-21 7:03 ` [PATCH v3 0/5] avoid double request completion and IO error Chao Leng 2021-01-21 7:03 ` [PATCH v3 1/5] blk-mq: introduce blk_mq_set_request_complete Chao Leng 2021-01-21 7:03 ` Chao Leng 2021-01-21 8:40 ` Christoph Hellwig 2021-01-21 8:40 ` Christoph Hellwig 2021-01-22 1:46 ` Chao Leng 2021-01-22 1:46 ` Chao Leng 2021-01-21 7:03 ` [PATCH v3 2/5] nvme-core: introduce complete failed request Chao Leng 2021-01-21 7:03 ` Chao Leng 2021-01-21 8:41 ` Christoph Hellwig 2021-01-21 8:41 ` Christoph Hellwig 2021-01-22 1:46 ` Chao Leng 2021-01-22 1:46 ` Chao Leng 2021-01-21 7:03 ` [PATCH v3 3/5] nvme-fabrics: avoid double request completion for nvmf_fail_nonready_command Chao Leng 2021-01-21 7:03 ` Chao Leng 2021-01-21 8:58 ` Hannes Reinecke 2021-01-21 8:58 ` Hannes Reinecke 2021-01-21 9:00 ` Christoph Hellwig 2021-01-21 9:00 ` Christoph Hellwig 2021-01-21 9:27 ` Hannes Reinecke 2021-01-21 9:27 ` Hannes Reinecke 2021-01-22 1:50 ` Chao Leng 2021-01-22 1:50 ` Chao Leng 2021-01-22 1:48 ` Chao Leng 2021-01-22 1:48 ` Chao Leng 2021-01-21 7:03 ` [PATCH v3 4/5] nvme-rdma: avoid IO error for nvme native multipath Chao Leng 2021-01-21 7:03 ` Chao Leng 2021-01-21 7:03 ` [PATCH v3 5/5] nvme-fc: " Chao Leng 2021-01-21 7:03 ` Chao Leng
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210121070330.19701-1-lengchao@huawei.com \ --to=lengchao@huawei.com \ --cc=axboe@fb.com \ --cc=axboe@kernel.dk \ --cc=hch@lst.de \ --cc=kbusch@kernel.org \ --cc=linux-block@vger.kernel.org \ --cc=linux-nvme@lists.infradead.org \ --cc=sagi@grimberg.me \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.