From: hare@suse.de (Hannes Reinecke)
Subject: [PATCH] nvme: schedule requeue whenever a LIVE state is entered
Date: Thu, 21 Mar 2019 15:10:33 +0100 [thread overview]
Message-ID: <20190321141033.131308-1-hare@suse.de> (raw)
When undergoing state transitions I/O might be requeued, hence
we always have to schedule requeue_work whenever the nvme device
is live, independent on whether the old state was live or not.
Reported-by: Martin George <martin.george at netapp.com>
Signed-off-by: Hannes Reinecke <hare at suse.com>
---
drivers/nvme/host/multipath.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/nvme/host/multipath.c b/drivers/nvme/host/multipath.c
index 2839bb70badf..f69c9476d663 100644
--- a/drivers/nvme/host/multipath.c
+++ b/drivers/nvme/host/multipath.c
@@ -352,8 +352,6 @@ static void nvme_mpath_set_live(struct nvme_ns *ns)
__nvme_find_path(head, node);
srcu_read_unlock(&head->srcu, srcu_idx);
}
-
- kblockd_schedule_work(&ns->head->requeue_work);
}
static int nvme_parse_ana_log(struct nvme_ctrl *ctrl, void *data,
@@ -412,8 +410,11 @@ static void nvme_update_ns_ana_state(struct nvme_ana_group_desc *desc,
ns->ana_state = desc->state;
clear_bit(NVME_NS_ANA_PENDING, &ns->flags);
- if (nvme_state_is_live(ns->ana_state) && !nvme_state_is_live(old))
- nvme_mpath_set_live(ns);
+ if (nvme_state_is_live(ns->ana_state)) {
+ if (!nvme_state_is_live(old))
+ nvme_mpath_set_live(ns);
+ kblockd_schedule_work(&ns->head->requeue_work);
+ }
mutex_unlock(&ns->head->lock);
}
@@ -587,6 +588,7 @@ void nvme_mpath_add_disk(struct nvme_ns *ns, struct nvme_id_ns *id)
mutex_lock(&ns->head->lock);
ns->ana_state = NVME_ANA_OPTIMIZED;
nvme_mpath_set_live(ns);
+ kblockd_schedule_work(&ns->head->requeue_work);
mutex_unlock(&ns->head->lock);
}
}
--
2.16.4
next reply other threads:[~2019-03-21 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 14:10 Hannes Reinecke [this message]
2019-03-21 21:26 ` [PATCH] nvme: schedule requeue whenever a LIVE state is entered Sagi Grimberg
2019-03-22 6:55 ` Hannes Reinecke
2019-03-22 18:57 ` Sagi Grimberg
2019-03-22 21:14 ` Hannes Reinecke
2019-03-25 15:55 ` Sagi Grimberg
2019-03-27 8:37 ` Christoph Hellwig
2019-03-27 8:44 ` 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=20190321141033.131308-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