From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 3/3] nvme: Fail controller on timeouts during reset
Date: Sun, 11 Feb 2018 11:53:06 +0200 [thread overview]
Message-ID: <2f2b2f64-8ce4-89a7-20dd-5c29b3d4b4e7@grimberg.me> (raw)
In-Reply-To: <75313a79-29da-3ea1-dd5b-c3d0d8c9069d@oracle.com>
>> diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
>> index 7a2e4383c468..77929d35eae8 100644
>> --- a/drivers/nvme/host/pci.c
>> +++ b/drivers/nvme/host/pci.c
>> @@ -1212,11 +1212,15 @@ static enum blk_eh_timer_return nvme_timeout(struct request *req, bool reserved)
>> /*
>> * Shutdown immediately if controller times out while starting. The
>> * reset work will see the pci device disabled when it gets the forced
>> - * cancellation error. All outstanding requests are completed on
>> + * cancellation error. The driver won't see the status if it is waiting
>> + * on asynchronous comands, so we set the state to deleting to prevent
>> + * it from progressing. All outstanding requests are completed on
>> * shutdown, so we return BLK_EH_HANDLED.
>> */
>> switch (dev->ctrl.state) {
>> case NVME_CTRL_CONNECTING:
>
> It seems that Max's commit (Fix host side state machine) have not been committed.
> So it should be RECONNECTING here.
Actually, they are already in nvme-4.16-rc.
I'd like to pick these up as well once they converge (even
taking 1+3 would be a good start).
next prev parent reply other threads:[~2018-02-11 9:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 17:41 [PATCH 1/3] nvme-pci: Fix timeouts in connecting state Keith Busch
2018-02-09 17:41 ` [PATCH 2/3] nvme: Sync queues on controller resets Keith Busch
2018-02-10 1:55 ` jianchao.wang
2018-02-11 1:53 ` jianchao.wang
2018-02-12 21:46 ` Keith Busch
2018-04-18 2:26 ` jianchao.wang
2018-04-19 14:33 ` Keith Busch
2018-02-09 17:41 ` [PATCH 3/3] nvme: Fail controller on timeouts during reset Keith Busch
2018-02-11 8:26 ` jianchao.wang
2018-02-11 9:53 ` Sagi Grimberg [this message]
2018-02-12 7:59 ` jianchao.wang
2018-02-12 18:37 ` Sagi Grimberg
2018-02-13 2:21 ` jianchao.wang
2018-02-10 2:14 ` [PATCH 1/3] nvme-pci: Fix timeouts in connecting state jianchao.wang
2018-02-12 14:18 ` Keith Busch
2018-02-13 2:21 ` jianchao.wang
2018-02-13 2:33 ` jianchao.wang
2018-02-13 14:47 ` Keith Busch
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=2f2b2f64-8ce4-89a7-20dd-5c29b3d4b4e7@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