From: Jianchao Wang <jianchao.w.wang@oracle.com>
To: keith.busch@intel.com, axboe@fb.com, hch@lst.de, sagi@grimberg.me
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] nvme-pci: don't send delete cq command when allocate sq return -EINTR
Date: Thu, 24 May 2018 17:51:34 +0800 [thread overview]
Message-ID: <1527155494-1891-2-git-send-email-jianchao.w.wang@oracle.com> (raw)
In-Reply-To: <1527155494-1891-1-git-send-email-jianchao.w.wang@oracle.com>
When allocate sq in nvme_create_queue return -EINTR, it means the
allocate sq command times out and is completed with NVME_REQ_CANCELLED.
At the moment, the controller has been disabled and admin request
queue has been quiesced. Don't send delete cq command, otherwise,
it will incur io hang.
Signed-off-by: Jianchao Wang <jianchao.w.wang@oracle.com>
---
drivers/nvme/host/pci.c | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 70b79f2..4ce1c89 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -1478,7 +1478,15 @@ static int nvme_create_queue(struct nvme_queue *nvmeq, int qid)
goto out;
result = adapter_alloc_sq(dev, qid, nvmeq);
- if (result < 0)
+ /*
+ * If return -EINTR, it means the allocate sq command times out and is completed
+ * with NVME_REQ_CANCELLED. At the time, the controller has been disabled
+ * and admin request queue has been quiesced. So don't try to send delete cq
+ * command any more.
+ */
+ if (result == -EINTR)
+ goto out;
+ else if (result < 0)
goto release_cq;
/*
--
2.7.4
next prev parent reply other threads:[~2018-05-24 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 9:51 [PATCH 1/2] nvme-pci: set nvmeq->cq_vector after alloc cq/sq Jianchao Wang
2018-05-24 9:51 ` Jianchao Wang [this message]
2018-05-24 13:38 ` [PATCH 2/2] nvme-pci: don't send delete cq command when allocate sq return -EINTR Keith Busch
2018-05-24 13:36 ` [PATCH 1/2] nvme-pci: set nvmeq->cq_vector after alloc cq/sq Keith Busch
2018-05-25 8:53 ` Christoph Hellwig
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=1527155494-1891-2-git-send-email-jianchao.w.wang@oracle.com \
--to=jianchao.w.wang@oracle.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-kernel@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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).