diff options
| author | Chuck Lever <chuck.lever@oracle.com> | 2024-05-31 16:15:53 +0300 |
|---|---|---|
| committer | Chuck Lever <chuck.lever@oracle.com> | 2024-07-08 21:10:02 +0300 |
| commit | d1b586e75ec619dde1af47e21a41a6b1b51874c2 (patch) | |
| tree | a48fd250bb18f01e53e7b483272e584607fd4165 /tools/perf/scripts/python/task-analyzer.py | |
| parent | 283d28546234b1764a0a37cb3df30cc3321c75b4 (diff) | |
| download | linux-d1b586e75ec619dde1af47e21a41a6b1b51874c2.tar.xz | |
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>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions