diff options
author | Sagi Grimberg <sagi@grimberg.me> | 2017-05-04 13:33:12 +0300 |
---|---|---|
committer | Christoph Hellwig <hch@lst.de> | 2017-06-15 15:28:22 +0300 |
commit | c58bd1bf4d46a020b7a1aa0710bca8191d789caa (patch) | |
tree | f8f66b66deda21e69fac561ce1dba26bcd13d5af | |
parent | b282a88d910296facf89fd1088832f9b41fa00c5 (diff) | |
download | linux-c58bd1bf4d46a020b7a1aa0710bca8191d789caa.tar.xz |
nvme: Don't allow to reset a reconnecting controller
The reset operation is guaranteed to fail for all scenarios
but the esoteric case where in the last reconnect attempt
concurrent with the reset we happen to successfully reconnect.
We just deny initiating a reset if we are reconnecting.
Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Christoph Hellwig <hch@lst.de>
-rw-r--r-- | drivers/nvme/host/core.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c index 767bcc6caae0..6d53094f4b8e 100644 --- a/drivers/nvme/host/core.c +++ b/drivers/nvme/host/core.c @@ -157,7 +157,6 @@ bool nvme_change_ctrl_state(struct nvme_ctrl *ctrl, switch (old_state) { case NVME_CTRL_NEW: case NVME_CTRL_LIVE: - case NVME_CTRL_RECONNECTING: changed = true; /* FALLTHRU */ default: |