From: hare@suse.de (Hannes Reinecke)
Subject: [PATCH 0/3] nvme-fc: track state change failures
Date: Thu, 16 May 2019 10:37:37 +0200 [thread overview]
Message-ID: <20190516083740.95894-1-hare@suse.de> (raw)
Hi all,
this patchset improves logging in the nvme-fc driver if expcected
state changes fail, and fixes up one case where a failed state change
might lead to a stuck controller.
Hannes Reinecke (3):
nvme: separate out nvme_ctrl_state_name()
nvme-fc: track state change failures during reconnect
nvme-fc: fail reconnect if state change fails
drivers/nvme/host/core.c | 36 +++++++++++++++++++++++-------------
drivers/nvme/host/fc.c | 23 +++++++++++++++++------
drivers/nvme/host/nvme.h | 1 +
3 files changed, 41 insertions(+), 19 deletions(-)
--
2.16.4
next reply other threads:[~2019-05-16 8:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 8:37 Hannes Reinecke [this message]
2019-05-16 8:37 ` [PATCH 1/3] nvme: separate out nvme_ctrl_state_name() Hannes Reinecke
2019-05-16 13:55 ` Minwoo Im
2019-05-16 16:24 ` James Smart
2019-05-16 8:37 ` [PATCH 2/3] nvme-fc: track state change failures during reconnect Hannes Reinecke
2019-05-16 16:24 ` James Smart
2019-05-16 8:37 ` [PATCH 3/3] nvme-fc: fail reconnect if state change fails Hannes Reinecke
2019-05-16 16:25 ` James Smart
2019-05-18 0:18 ` Arun Easi
2019-05-18 0:21 ` Arun Easi
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=20190516083740.95894-1-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.