From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <keith.busch@wdc.com>,
linux-nvme@lists.infradead.org, Hannes Reinecke <hare@suse.de>
Subject: [PATCH] nvme: allow to re-attach namespaces after all paths are down
Date: Mon, 10 May 2021 16:49:06 +0200 [thread overview]
Message-ID: <20210510144906.8305-1-hare@suse.de> (raw)
We should only remove the ns head from the list of heads per
subsystem if the reference count drops to zero. Removing it
at the start of nvme_ns_remove() will prevent us from reattaching
the namespace to the correct ns head once a path becomes available
again.
Signed-off-by: Hannes Reinecke <hare@suse.de>
---
drivers/nvme/host/core.c | 33 ++++++++++++++++++++++-----------
1 file changed, 22 insertions(+), 11 deletions(-)
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index 762125f2905f..08ff0fc01f9e 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -546,6 +546,9 @@ static void nvme_free_ns_head(struct kref *ref)
struct nvme_ns_head *head =
container_of(ref, struct nvme_ns_head, ref);
+ mutex_lock(&head->subsys->lock);
+ list_del_init(&head->entry);
+ mutex_unlock(&head->subsys->lock);
nvme_mpath_remove_disk(head);
ida_simple_remove(&head->subsys->ns_ida, head->instance);
cleanup_srcu_struct(&head->srcu);
@@ -3605,16 +3608,26 @@ static int nvme_init_ns_head(struct nvme_ns *ns, unsigned nsid,
head->shared = is_shared;
} else {
ret = -EINVAL;
- if (!is_shared || !head->shared) {
- dev_err(ctrl->device,
- "Duplicate unshared namespace %d\n", nsid);
- goto out_put_ns_head;
- }
- if (!nvme_ns_ids_equal(&head->ids, ids)) {
- dev_err(ctrl->device,
- "IDs don't match for shared namespace %d\n",
+ /*
+ * If multipath is enabled we might hit an ns head with no
+ * paths, but that doesn't indicate it's a shared namespace.
+ */
+ if (!nvme_ns_head_multipath(head) ||
+ !list_empty(&head->list)) {
+ if (!is_shared || !head->shared) {
+ dev_err(ctrl->device,
+ "Duplicate unshared namespace %d\n", nsid);
+ goto out_put_ns_head;
+ }
+ if (!nvme_ns_ids_equal(&head->ids, ids)) {
+ dev_err(ctrl->device,
+ "IDs don't match for shared namespace %d\n",
nsid);
- goto out_put_ns_head;
+ goto out_put_ns_head;
+ }
+ } else {
+ /* But the ids might have changed, so reset them */
+ head->ids = *ids;
}
}
@@ -3764,8 +3777,6 @@ static void nvme_ns_remove(struct nvme_ns *ns)
mutex_lock(&ns->ctrl->subsys->lock);
list_del_rcu(&ns->siblings);
- if (list_empty(&ns->head->list))
- list_del_init(&ns->head->entry);
mutex_unlock(&ns->ctrl->subsys->lock);
synchronize_rcu(); /* guarantee not available in head->list */
--
2.26.2
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-05-10 14:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 14:49 Hannes Reinecke [this message]
2021-05-10 15:53 ` [PATCH] nvme: allow to re-attach namespaces after all paths are down Keith Busch
2021-05-10 22:25 ` Sagi Grimberg
2021-05-11 5:57 ` Hannes Reinecke
2021-05-11 17:02 ` Sagi Grimberg
2021-05-12 6:05 ` Hannes Reinecke
2021-05-11 21:37 ` Keith Busch
2021-05-12 13:18 ` Hannes Reinecke
2021-05-12 20:51 ` Sagi Grimberg
2021-05-11 5:29 ` Hannes Reinecke
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=20210510144906.8305-1-hare@suse.de \
--to=hare@suse.de \
--cc=hch@lst.de \
--cc=keith.busch@wdc.com \
--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