> On Jun 2, 2024, at 3:50 AM, Sagi Grimberg <sagi@xxxxxxxxxxx> wrote: > > > > On 31/05/2024 16:15, cel@xxxxxxxxxx wrote: >> From: Chuck Lever <chuck.lever@xxxxxxxxxx> >> >> Sagi recently pointed out that the CM ADDR_CHANGE event handler in >> svcrdma has a bug similar to one he fixed in the NVMe target. This >> series attempts to address that issue. >> >> Chuck Lever (2): >> svcrdma: Refactor the creation of listener CMA ID >> svcrdma: Handle ADDR_CHANGE CM event properly >> >> net/sunrpc/xprtrdma/svc_rdma_transport.c | 83 ++++++++++++++++-------- >> 1 file changed, 55 insertions(+), 28 deletions(-) >> > > Looks good, For the series: > > Reviewed-by: Sagi Grimberg <sagi@xxxxxxxxxxx> Thank you! Applied to nfsd-next (for 6.11). -- Chuck Lever