From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 2/4] NVMe: Sync stopped queues with block layer
Date: Wed, 3 Feb 2016 09:05:41 -0700 [thread overview]
Message-ID: <1454515543-21683-3-git-send-email-keith.busch@intel.com> (raw)
In-Reply-To: <1454515543-21683-1-git-send-email-keith.busch@intel.com>
Make sure no work will submit requests to a stopped h/w queue.
Signed-off-by: Keith Busch <keith.busch at intel.com>
---
drivers/nvme/host/core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index c5bf001..9d415489 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -1415,6 +1415,7 @@ void nvme_stop_queues(struct nvme_ctrl *ctrl)
blk_mq_cancel_requeue_work(ns->queue);
blk_mq_stop_hw_queues(ns->queue);
+ blk_sync_queue(ns->queue);
}
mutex_unlock(&ctrl->namespaces_mutex);
}
--
2.6.2.307.g37023ba
next prev parent reply other threads:[~2016-02-03 16:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 16:05 [PATCH 0/4] NVMe: Surprise removal fixes Keith Busch
2016-02-03 16:05 ` [PATCH 1/4] NVMe: Fix io incapable return values Keith Busch
2016-02-04 15:55 ` Sagi Grimberg
2016-02-08 18:10 ` Christoph Hellwig
2016-02-03 16:05 ` Keith Busch [this message]
2016-02-04 15:57 ` [PATCH 2/4] NVMe: Sync stopped queues with block layer Sagi Grimberg
2016-02-04 16:00 ` Keith Busch
2016-02-08 18:11 ` Christoph Hellwig
2016-02-03 16:05 ` [PATCH 3/4] NVMe: Surprise removal fixes Keith Busch
2016-02-08 18:16 ` Christoph Hellwig
2016-02-08 18:38 ` Keith Busch
2016-02-08 23:48 ` Keith Busch
2016-02-03 16:05 ` [PATCH 4/4] blk-mq: End unstarted requests on dying queue Keith Busch
2016-02-04 15:59 ` Sagi Grimberg
2016-02-08 18:13 ` Christoph Hellwig
2016-02-04 3:25 ` [PATCH 0/4] NVMe: Surprise removal fixes Wenbo Wang
2016-02-04 15:52 ` Keith Busch
2016-02-04 15:55 ` Sagi Grimberg
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=1454515543-21683-3-git-send-email-keith.busch@intel.com \
--to=keith.busch@intel.com \
/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 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.