projects / linux-2.6-block.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 283d285) | patch
svcrdma: Handle ADDR_CHANGE CM event properly
authorChuck Lever <chuck.lever@oracle.com>
Fri, 31 May 2024 13:15:53 +0000 (09:15 -0400)
committerChuck Lever <chuck.lever@oracle.com>
Mon, 8 Jul 2024 18:10:02 +0000 (14:10 -0400)
commitd1b586e75ec619dde1af47e21a41a6b1b51874c2
treea48fd250bb18f01e53e7b483272e584607fd4165tree | snapshot
parent283d28546234b1764a0a37cb3df30cc3321c75b4commit | diff
svcrdma: Handle ADDR_CHANGE CM event properly

Sagi tells me that when a bonded device reports an address change,
the consumer must destroy its listener IDs and create new ones.

See commit a032e4f6d60d ("nvmet-rdma: fix bonding failover possible
NULL deref").

Suggested-by: Sagi Grimberg <sagi@grimberg.me>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
net/sunrpc/xprtrdma/svc_rdma_transport.c diff | blob | blame | history
Linux 6.x block layer and io_uring tree(s)