From: hare@suse.de (Hannes Reinecke)
Subject: [PATCH 2/2] nvme: protect against race condition in nvme_validate_ns()
Date: Tue, 19 Feb 2019 13:13:58 +0100 [thread overview]
Message-ID: <20190219121358.57975-3-hare@suse.de> (raw)
In-Reply-To: <20190219121358.57975-1-hare@suse.de>
When subsystems are rapidly reconfigured (or sending out several AENs)
we might end up in a situation where several instances of nvme_scan_work()
are running. Each of which might be trying to register the same nsid,
so nvme_find_get_ns() in nvme_validate_ns() will return 0 for both,
resulting in a crash in nvme_alloc_ns() as both are registering a
gendisk with the same name.
Signed-off-by: Hannes Reinecke <hare at suse.com>
---
drivers/nvme/host/core.c | 20 +++++++++++++++++---
1 file changed, 17 insertions(+), 3 deletions(-)
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index 9c6f6a4db60a..7cf710e8d98d 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -3216,7 +3216,7 @@ static int nvme_setup_streams_ns(struct nvme_ctrl *ctrl, struct nvme_ns *ns)
static int nvme_alloc_ns(struct nvme_ctrl *ctrl, unsigned nsid)
{
- struct nvme_ns *ns;
+ struct nvme_ns *ns, *tmp;
struct gendisk *disk;
struct nvme_id_ns *id;
char disk_name[DISK_NAME_LEN];
@@ -3286,6 +3286,15 @@ static int nvme_alloc_ns(struct nvme_ctrl *ctrl, unsigned nsid)
}
down_write(&ctrl->namespaces_rwsem);
+ list_for_each_entry(tmp, &ctrl->namespaces, list) {
+ if (nsid == tmp->head->ns_id) {
+ up_write(&ctrl->namespaces_rwsem);
+ dev_warn(ctrl->device,
+ "Duplicate ns %d, rescanning", nsid);
+ ret = -EAGAIN;
+ goto out_put_disk;
+ }
+ }
list_add_tail(&ns->list, &ctrl->namespaces);
up_write(&ctrl->namespaces_rwsem);
@@ -3343,14 +3352,19 @@ static void nvme_ns_remove(struct nvme_ns *ns)
static void nvme_validate_ns(struct nvme_ctrl *ctrl, unsigned nsid)
{
struct nvme_ns *ns;
+ int ret;
+rescan:
ns = nvme_find_get_ns(ctrl, nsid);
if (ns) {
if (ns->disk && revalidate_disk(ns->disk))
nvme_ns_remove(ns);
nvme_put_ns(ns);
- } else
- nvme_alloc_ns(ctrl, nsid);
+ } else {
+ ret = nvme_alloc_ns(ctrl, nsid);
+ if (ret == -EAGAIN)
+ goto rescan;
+ }
}
static void nvme_remove_invalid_namespaces(struct nvme_ctrl *ctrl,
--
2.16.4
next prev parent reply other threads:[~2019-02-19 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 12:13 [PATCH 0/2] nvme: fixup crash in device_add_disk() Hannes Reinecke
2019-02-19 12:13 ` [PATCH 1/2] nvme: return error from nvme_alloc_ns() Hannes Reinecke
2019-02-19 19:42 ` Sagi Grimberg
2019-02-20 14:21 ` Christoph Hellwig
2019-02-19 12:13 ` Hannes Reinecke [this message]
2019-02-19 19:44 ` [PATCH 2/2] nvme: protect against race condition in nvme_validate_ns() Sagi Grimberg
2019-02-19 19:54 ` Keith Busch
2019-02-20 6:52 ` 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=20190219121358.57975-3-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