diff options
| author | Chuck Lever <[email protected]> | 2024-05-31 09:15:53 -0400 |
|---|---|---|
| committer | Chuck Lever <[email protected]> | 2024-07-08 14:10:02 -0400 |
| commit | d1b586e75ec619dde1af47e21a41a6b1b51874c2 (patch) | |
| tree | a48fd250bb18f01e53e7b483272e584607fd4165 /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | 283d28546234b1764a0a37cb3df30cc3321c75b4 (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 <[email protected]>
Reviewed-by: Sagi Grimberg <[email protected]>
Signed-off-by: Chuck Lever <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions