From: jianchao.w.wang@oracle.com (jianchao.wang)
Subject: [PATCH V3 7/8] nvme: pci: recover controller reliably
Date: Fri, 4 May 2018 14:21:57 +0800 [thread overview]
Message-ID: <ee550e2f-d8c2-1633-3e49-9d4e201d080b@oracle.com> (raw)
In-Reply-To: <2e6e88f9-089a-2809-0c2b-4e96ba1199e9@oracle.com>
Oh sorry.
On 05/04/2018 02:10 PM, jianchao.wang wrote:
> nvme_error_handler should invoke nvme_reset_ctrl instead of introducing another interface.
> Then it is more convenient to ensure that there will be only one resetting instance running.
ctrl state is still in RESETTING state, nvme_reset_ctrl cannot work.
Thanks
Jianchao
next prev parent reply other threads:[~2018-05-04 6:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 3:17 [PATCH V3 0/8] nvme: pci: fix & improve timeout handling Ming Lei
2018-05-03 3:17 ` [PATCH V3 1/8] block: introduce blk_quiesce_timeout() and blk_unquiesce_timeout() Ming Lei
2018-05-03 3:17 ` [PATCH V3 2/8] nvme: pci: cover timeout for admin commands running in EH Ming Lei
2018-05-03 3:17 ` [PATCH V3 3/8] nvme: pci: only wait freezing if queue is frozen Ming Lei
2018-05-03 3:17 ` [PATCH V3 4/8] nvme: pci: freeze queue in nvme_dev_disable() in case of error recovery Ming Lei
2018-05-03 3:17 ` [PATCH V3 5/8] nvme: fix race between freeze queues and unfreeze queues Ming Lei
2018-05-03 3:17 ` [PATCH V3 6/8] nvme: pci: split controller resetting into two parts Ming Lei
2018-05-03 3:17 ` [PATCH V3 7/8] nvme: pci: recover controller reliably Ming Lei
2018-05-03 9:14 ` jianchao.wang
2018-05-03 10:08 ` Ming Lei
2018-05-03 15:46 ` jianchao.wang
2018-05-04 4:24 ` Ming Lei
2018-05-04 6:10 ` jianchao.wang
2018-05-04 6:21 ` jianchao.wang [this message]
2018-05-04 8:02 ` Ming Lei
2018-05-04 8:28 ` jianchao.wang
2018-05-04 9:16 ` Ming Lei
2018-05-05 0:16 ` Ming Lei
2018-05-03 3:17 ` [PATCH V3 8/8] nvme: pci: simplify timeout handling Ming Lei
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=ee550e2f-d8c2-1633-3e49-9d4e201d080b@oracle.com \
--to=jianchao.w.wang@oracle.com \
/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