From: hare@suse.de (Hannes Reinecke)
Subject: [PATCH 3/4] nvme-fc: fail reconnect if state change fails
Date: Mon, 20 May 2019 08:36:23 +0200 [thread overview]
Message-ID: <20190520063624.50338-4-hare@suse.de> (raw)
In-Reply-To: <20190520063624.50338-1-hare@suse.de>
If the final state change to LIVE in nvme_fc_create_association()
fails the controller is not operational as no I/O is possible.
So we should be returning an error here to reschedule reconnect.
Additionally it should only be called while in CONNECTING state, so
add a check for this, too.
Signed-off-by: Hannes Reinecke <hare at suse.com>
---
drivers/nvme/host/fc.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/drivers/nvme/host/fc.c b/drivers/nvme/host/fc.c
index e5c81ba2b7a1..71b22139e78b 100644
--- a/drivers/nvme/host/fc.c
+++ b/drivers/nvme/host/fc.c
@@ -2624,6 +2624,14 @@ nvme_fc_create_association(struct nvme_fc_ctrl *ctrl)
++ctrl->ctrl.nr_reconnects;
+ if (ctrl->ctrl.state != NVME_CTRL_CONNECTING) {
+ dev_info(ctrl->ctrl.device,
+ "NVME-FC{%d}: state %s cancelled new "
+ "association attempt\n",
+ ctrl->cnum, nvme_ctrl_state_name(&ctrl->ctrl));
+ return -ENODEV;
+ }
+
if (ctrl->rport->remoteport.port_state != FC_OBJSTATE_ONLINE)
return -ENODEV;
@@ -2726,6 +2734,14 @@ nvme_fc_create_association(struct nvme_fc_ctrl *ctrl)
}
changed = nvme_change_ctrl_state(&ctrl->ctrl, NVME_CTRL_LIVE);
+ if (!changed && ctrl->ctrl.state != NVME_CTRL_DELETING) {
+ dev_err(ctrl->ctrl.device,
+ "NVME-FC{%d}: error_recovery: Couldn't change "
+ "state from %s to LIVE\n", ctrl->cnum,
+ nvme_ctrl_state_name(&ctrl->ctrl));
+ ret = -EAGAIN;
+ goto out_destroy_queues;
+ }
ctrl->ctrl.nr_reconnects = 0;
@@ -2734,6 +2750,9 @@ nvme_fc_create_association(struct nvme_fc_ctrl *ctrl)
return 0; /* Success */
+out_destroy_queues:
+ nvme_fc_delete_hw_io_queues(ctrl);
+ nvme_fc_free_io_queues(ctrl);
out_term_aen_ops:
nvme_fc_term_aen_ops(ctrl);
out_disconnect_admin_queue:
--
2.16.4
next prev parent reply other threads:[~2019-05-20 6:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 6:36 [PATCH 0/4v3] nvme-fc: track state change failures Hannes Reinecke
2019-05-20 6:36 ` [PATCH 1/4] nvme: separate out nvme_ctrl_state_name() Hannes Reinecke
2019-05-21 6:46 ` Christoph Hellwig
2019-05-24 6:46 ` Sagi Grimberg
2019-05-24 7:33 ` Hannes Reinecke
2019-05-24 20:34 ` Keith Busch
2019-05-20 6:36 ` [PATCH 2/4] nvme-fc: track state change failures during reconnect Hannes Reinecke
2019-05-21 6:47 ` Christoph Hellwig
2019-05-24 6:51 ` Sagi Grimberg
2019-05-24 7:35 ` Hannes Reinecke
2019-05-20 6:36 ` Hannes Reinecke [this message]
2019-05-21 16:18 ` [PATCH 3/4] nvme-fc: fail reconnect if state change fails James Smart
2019-05-22 17:43 ` Arun Easi
2019-05-23 5:33 ` Hannes Reinecke
2019-05-23 15:46 ` James Smart
2019-05-23 15:52 ` [EXT] " Arun Easi
2019-05-20 6:36 ` [PATCH 4/4] nvme-fc: align nvme_fc_delete_association() with exit path Hannes Reinecke
2019-05-21 16:25 ` James Smart
2019-05-22 14:00 ` Hannes Reinecke
2019-05-23 16:01 ` James Smart
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=20190520063624.50338-4-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 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.