diff options
| author |   Johannes Thumshirn <jthumshirn@suse.de> | 2018-05-03 17:00:35 +0200 |
|---|---|---|
| committer |   Jens Axboe <axboe@kernel.dk> | 2018-05-03 09:37:50 -0600 |
| commit | 8bfc3b4c6f9de815de4ab73784b9419348266a65 (patch) | |
| tree | 0f2bf8c50e46896b0f37efcaa3c3642bc5fed3f7 /fs/fs-writeback.c | |
| parent | nvme/multipath: Fix multipath disabled naming collisions (diff) | |
| download | linux-dev-8bfc3b4c6f9de815de4ab73784b9419348266a65.tar.xz linux-dev-8bfc3b4c6f9de815de4ab73784b9419348266a65.zip | |
nvmet: switch loopback target state to connecting when resetting
After commit bb06ec31452f ("nvme: expand nvmf_check_if_ready checks")
resetting of the loopback nvme target failed as we forgot to switch
it's state to NVME_CTRL_CONNECTING before we reconnect the admin
queues. Therefore the checks in nvmf_check_if_ready() choose to go to
the reject_io case and thus we couldn't sent out an identify
controller command to reconnect.
Change the controller state to NVME_CTRL_CONNECTING after tearing down
the old connection and before re-establishing the connection.
Fixes: bb06ec31452f ("nvme: expand nvmf_check_if_ready checks")
Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
Signed-off-by: Keith Busch <keith.busch@intel.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'fs/fs-writeback.c')
0 files changed, 0 insertions, 0 deletions