diff options
author | Sagi Grimberg <sagi@grimberg.me> | 2020-08-05 18:13:58 -0700 |
---|---|---|
committer | Sagi Grimberg <sagi@grimberg.me> | 2020-08-28 16:43:57 -0700 |
commit | 5110f40241d08334375eb0495f174b1d2c07657e (patch) | |
tree | d170c9469641eeb92535fe4a1904f335daa9e701 /net | |
parent | e5c01f4f7f623e768e868bcc08d8e7ceb03b75d0 (diff) | |
download | linux-5110f40241d08334375eb0495f174b1d2c07657e.tar.bz2 |
nvme-rdma: serialize controller teardown sequences
In the timeout handler we may need to complete a request because the
request that timed out may be an I/O that is a part of a serial sequence
of controller teardown or initialization. In order to complete the
request, we need to fence any other context that may compete with us
and complete the request that is timing out.
In this case, we could have a potential double completion in case
a hard-irq or a different competing context triggered error recovery
and is running inflight request cancellation concurrently with the
timeout handler.
Protect using a ctrl teardown_lock to serialize contexts that may
complete a cancelled request due to error recovery or a reset.
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: James Smart <james.smart@broadcom.com>
Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions