diff options
| author | Dan Aloni <[email protected]> | 2024-05-06 09:37:59 +0000 |
|---|---|---|
| committer | Trond Myklebust <[email protected]> | 2024-05-20 15:37:15 +0000 |
| commit | 4836da219781ec510c4c0303df901aa643507a7a (patch) | |
| tree | 3a9fefd07838db64b2fc47c42b2c5447e93b8a95 /drivers/gpu/drm/amd/amdgpu/amdgpu_ucode.c | |
| parent | NFS: Don't enable NFS v2 by default (diff) | |
| download | kernel-4836da219781ec510c4c0303df901aa643507a7a.tar.gz kernel-4836da219781ec510c4c0303df901aa643507a7a.zip | |
rpcrdma: fix handling for RDMA_CM_EVENT_DEVICE_REMOVAL
Under the scenario of IB device bonding, when bringing down one of the
ports, or all ports, we saw xprtrdma entering a non-recoverable state
where it is not even possible to complete the disconnect and shut it
down the mount, requiring a reboot. Following debug, we saw that
transport connect never ended after receiving the
RDMA_CM_EVENT_DEVICE_REMOVAL callback.
The DEVICE_REMOVAL callback is irrespective of whether the CM_ID is
connected, and ESTABLISHED may not have happened. So need to work with
each of these states accordingly.
Fixes: 2acc5cae2923 ('xprtrdma: Prevent dereferencing r_xprt->rx_ep after it is freed')
Cc: Sagi Grimberg <[email protected]>
Signed-off-by: Dan Aloni <[email protected]>
Reviewed-by: Sagi Grimberg <[email protected]>
Reviewed-by: Chuck Lever <[email protected]>
Signed-off-by: Trond Myklebust <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_ucode.c')
0 files changed, 0 insertions, 0 deletions