From: hare@suse.de (Hannes Reinecke)
Subject: [PATCH 1/3] nvme: also check for RESETTING state in nvmf_check_if_ready()
Date: Thu, 7 Jun 2018 10:38:45 +0200 [thread overview]
Message-ID: <20180607083847.51019-2-hare@suse.de> (raw)
In-Reply-To: <20180607083847.51019-1-hare@suse.de>
When resetting the controller some transports go into 'RESETTING' state
before issuing the actual 'reset' command. So add the 'RESETTING' state
to nvmf_check_if_ready() to give them a chance to submit it.
Signed-off-by: Hannes Reinecke <hare at suse.com>
---
drivers/nvme/host/fabrics.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/nvme/host/fabrics.c b/drivers/nvme/host/fabrics.c
index fa32c1216409..909dd337221a 100644
--- a/drivers/nvme/host/fabrics.c
+++ b/drivers/nvme/host/fabrics.c
@@ -548,6 +548,7 @@ blk_status_t nvmf_check_if_ready(struct nvme_ctrl *ctrl, struct request *rq,
case NVME_CTRL_NEW:
case NVME_CTRL_CONNECTING:
case NVME_CTRL_DELETING:
+ case NVME_CTRL_RESETTING:
/*
* This is the case of starting a new or deleting an association
* but connectivity was lost before it was fully created or torn
--
2.12.3
next prev parent reply other threads:[~2018-06-07 8:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 8:38 [PATCH 0/3] misc nvme fixes Hannes Reinecke
2018-06-07 8:38 ` Hannes Reinecke [this message]
2018-06-07 8:41 ` [PATCH 1/3] nvme: also check for RESETTING state in nvmf_check_if_ready() Sagi Grimberg
2018-06-07 11:26 ` Christoph Hellwig
2018-06-12 21:20 ` James Smart
2018-06-07 8:38 ` [PATCH 2/3] nvme: do not access request after calling blk_mq_end_request() Hannes Reinecke
2018-06-07 8:42 ` Sagi Grimberg
2018-06-07 11:27 ` Christoph Hellwig
2018-06-07 8:38 ` [PATCH 3/3] nvme: bio remapping tracepoint Hannes Reinecke
2018-06-07 8:41 ` Sagi Grimberg
2018-06-07 11:27 ` Christoph Hellwig
2018-06-07 11:33 ` Hannes Reinecke
2018-06-07 11:42 ` Christoph Hellwig
2018-06-07 16:21 ` Jens Axboe
2018-06-11 14:26 ` 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=20180607083847.51019-2-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