From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 1/2] nvme-rdma: reuse nvme_delete_ctrl when reconnect attempts expire
Date: Sun, 29 Oct 2017 14:21:01 +0200 [thread overview]
Message-ID: <1509279662-32169-1-git-send-email-sagi@grimberg.me> (raw)
instead of just queueing delete work
Reported-by: Christoph Hellwig <hch at lst.de>
Signed-off-by: Sagi Grimberg <sagi at grimberg.me>
---
drivers/nvme/host/rdma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nvme/host/rdma.c b/drivers/nvme/host/rdma.c
index 4f8a249a2c12..5e95a9860f35 100644
--- a/drivers/nvme/host/rdma.c
+++ b/drivers/nvme/host/rdma.c
@@ -912,7 +912,7 @@ static void nvme_rdma_reconnect_or_remove(struct nvme_rdma_ctrl *ctrl)
ctrl->ctrl.opts->reconnect_delay * HZ);
} else {
dev_info(ctrl->ctrl.device, "Removing controller...\n");
- queue_work(nvme_wq, &ctrl->ctrl.delete_work);
+ nvme_delete_ctrl(&ctrl->ctrl);
}
}
--
2.7.4
next reply other threads:[~2017-10-29 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 12:21 Sagi Grimberg [this message]
2017-10-29 12:21 ` [PATCH 2/2] nvme-core: flush reset_work before safely continuing with delete operation Sagi Grimberg
2017-11-01 15:17 ` [PATCH 1/2] nvme-rdma: reuse nvme_delete_ctrl when reconnect attempts expire 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=1509279662-32169-1-git-send-email-sagi@grimberg.me \
--to=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;
as well as URLs for NNTP newsgroup(s).