diff options
author | James Smart <jsmart2021@gmail.com> | 2017-10-25 16:43:14 -0700 |
---|---|---|
committer | Christoph Hellwig <hch@lst.de> | 2017-11-01 16:28:23 +0100 |
commit | 44c6ec77e12c387aaba420b30a54b94966f0d9e8 (patch) | |
tree | 21fb28e9cc2fa7a1e62c7ad6c20c1739ec9e36ff /include/linux/nvme-fc-driver.h | |
parent | nvme: flush reset_work before safely continuing with delete operation (diff) | |
download | wireguard-linux-44c6ec77e12c387aaba420b30a54b94966f0d9e8.tar.xz wireguard-linux-44c6ec77e12c387aaba420b30a54b94966f0d9e8.zip |
nvme-fc: change ctlr state assignments during reset/reconnect
Clean up some of the controller state checks and add the
RESETTING->RECONNECTING state transition.
Specifically:
- the movement of the RESETTING state change and schedule of reset_work
to core doesn't work wiht nvme_fc_error_recovery setting state to
RECONNECTING before attempting to reset. Remove the state change as
the reset request does it.
- In the rare cases where an error occurs right as we're transitioning
to LIVE, defer the controller start actions.
- In error handling on teardown of associations while performing initial
controller creation - avoid quiesce calls on the admin_q. They are
unneeded.
- Add the RESETTING->RECONNECTING transition in the reset handler.
Signed-off-by: James Smart <james.smart@broadcom.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'include/linux/nvme-fc-driver.h')
0 files changed, 0 insertions, 0 deletions