diff options
| author | James Smart <jsmart2021@gmail.com> | 2017-07-18 23:29:34 +0200 |
|---|---|---|
| committer | Christoph Hellwig <hch@lst.de> | 2017-07-25 17:58:47 +0200 |
| commit | 8b25f351929b5a5216ccb2c8882965134019679d (patch) | |
| tree | 8583abf057bf94ccafe3b5877023bb09ec85c178 /drivers/nvme/target | |
| parent | nvme: fabrics commands should use the fctype field for data direction (diff) | |
| download | linux-8b25f351929b5a5216ccb2c8882965134019679d.tar.xz linux-8b25f351929b5a5216ccb2c8882965134019679d.zip | |
nvme-fc: address target disconnect race conditions in fcp io submit
There are cases where threads are in the process of submitting new
io when the LLDD calls in to remove the remote port. In some cases,
the next io actually goes to the LLDD, who knows the remoteport isn't
present and rejects it. To properly recovery/restart these i/o's we
don't want to hard fail them, we want to treat them as temporary
resource errors in which a delayed retry will work.
Add a couple more checks on remoteport connectivity and commonize the
busy response handling when it's seen.
Signed-off-by: James Smart <james.smart@broadcom.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'drivers/nvme/target')
0 files changed, 0 insertions, 0 deletions