From: hare@suse.de (Hannes Reinecke)
Subject: [PATCH] nvme: do not block connect call on inaccessible devices
Date: Tue, 5 Jun 2018 10:29:05 +0200 [thread overview]
Message-ID: <20180605082905.1740-1-hare@suse.de> (raw)
When a device is in ANA inaccessible state the call to 'nvme connect'
will hang as a parition scan is triggered and the I/O will be requeued
indefinitely.
Or rather, requeued until the next path is connected, but we cannot issue
any nvme ioctls anymore as the nvmf_dev_mutex is blocked by the initial
'connect' call.
This patch inhibits partition scan if no working paths are found, and
retriggers the partition scan once the device becomes active.
Signed-off-by: Hannes Reinecke <hare at suse.com>
---
drivers/nvme/host/multipath.c | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/drivers/nvme/host/multipath.c b/drivers/nvme/host/multipath.c
index 14bcc51016c7..30ba3c43e541 100644
--- a/drivers/nvme/host/multipath.c
+++ b/drivers/nvme/host/multipath.c
@@ -275,16 +275,44 @@ int nvme_mpath_alloc_disk(struct nvme_ctrl *ctrl, struct nvme_ns_head *head)
void nvme_mpath_add_disk(struct nvme_ns_head *head)
{
+ struct nvme_ns *ns;
+ int nr_working = 0;
+
if (!head->disk)
return;
mutex_lock(&head->subsys->lock);
+ list_for_each_entry(ns, &head->list, siblings) {
+ if (nvme_ns_ana_state(ns) == NVME_ANA_OPTIMIZED ||
+ nvme_ns_ana_state(ns) == NVME_ANA_NONOPTIMIZED)
+ nr_working++;
+ }
+ /* Disable partition scan if no working paths are found */
+ if (!nr_working)
+ head->disk->flags |= GENHD_FL_NO_PART_SCAN;
+ else
+ head->disk->flags &= ~GENHD_FL_NO_PART_SCAN;
+
if (!(head->disk->flags & GENHD_FL_UP)) {
device_add_disk(&head->subsys->dev, head->disk);
if (sysfs_create_group(&disk_to_dev(head->disk)->kobj,
&nvme_ns_id_attr_group))
pr_warn("%s: failed to create sysfs group for identification\n",
head->disk->disk_name);
+ } else {
+ struct block_device *bdev;
+
+ /*
+ * We need to do an explicit blkdev_get() to
+ * re-trigger partition scan if new paths have been added.
+ */
+ bdev = bdget_disk(head->disk, 0);
+ if (bdev) {
+ bdev->bd_invalidated = 1;
+ if (!blkdev_get(bdev, FMODE_READ, NULL))
+ blkdev_put(bdev, FMODE_READ);
+ bdput(bdev);
+ }
}
mutex_unlock(&head->subsys->lock);
}
--
2.12.3
next reply other threads:[~2018-06-05 8:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 8:29 Hannes Reinecke [this message]
2018-06-05 11:17 ` [PATCH] nvme: do not block connect call on inaccessible devices Christoph Hellwig
2018-06-05 12:23 ` Hannes Reinecke
2018-06-05 12:35 ` Bart Van Assche
2018-06-05 12:50 ` hch
2018-06-05 12:51 ` 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=20180605082905.1740-1-hare@suse.de \
--to=hare@suse.de \
/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