Re: [RFC PATCH 1/2] RDMA/rxe: drive UDP tunnel socket lifetime from the GID table

[Serhat Kumral <serhatkumral1@gmail.com>]

> Could you please run this selftest in your environment to see if you can
> reproduce the deadlock/hang and capture the stack trace?

I could not reproduce this.

I ran the exact sequence from rxe_rping_between_netns.sh, including
its cleanup order and module unload, on arm64 QEMU with KASAN,
lockdep and a 30-second hung-task timeout. rdma_rxe was built as a
module and the test used rdma-core's rping.

I ran it 15 consecutive times, followed by a variant that unloads
the module while the netns and RXE devices are still alive. The
rping transfers completed, the unload succeeded, and there were no
hangs or splats.

The series was based on b21d9bf627dd. Could you share your exact
base commit and .config, and confirm whether the same test passes
on that tree without this series?

The script redirects stdout to /dev/null, so could you also identify
the command at which it stops, for example by temporarily removing
the redirections and running it with bash -x? If it hangs again,
"echo w > /proc/sysrq-trigger" and, if possible,
"echo t > /proc/sysrq-trigger" from the console should provide the
blocked-task stacks without requiring kdump.