Comment 2 for bug 1923607

crash> bt 846786
PID: 846786 TASK: ffff9c2030da8000 CPU: 1 COMMAND: "(podman)"
 #0 [ffffc0998fe33c60] __schedule at ffffffffbd0d33f6
 #1 [ffffc0998fe33cf8] schedule at ffffffffbd0d3888
 #2 [ffffc0998fe33d08] schedule_timeout at ffffffffbd0d74a6
 #3 [ffffc0998fe33da0] unix_wait_for_peer at ffffffffbd03d44f
 #4 [ffffc0998fe33df0] unix_stream_connect at ffffffffbd0404ac
 #5 [ffffc0998fe33e70] __sys_connect at ffffffffbcf19c5a
 #6 [ffffc0998fe33f30] __x64_sys_connect at ffffffffbcf19ca6
 #7 [ffffc0998fe33f38] do_syscall_64 at ffffffffbc80419b
 #8 [ffffc0998fe33f50] entry_SYSCALL_64_after_hwframe at ffffffffbd2000ad
    RIP: 00007f8fdc558aa7 RSP: 00007ffdd43c8940 RFLAGS: 00000293
    RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f8fdc558aa7
    RDX: 000000000000001d RSI: 000055d5fc3f1c60 RDI: 0000000000000003
    RBP: 000055d5fc3f1c60 R8: 0000000000000000 R9: 00007ffdd43c8f14
    R10: 00007ffdd43c8bb8 R11: 0000000000000293 R12: 000000000000001d
    R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000003
    ORIG_RAX: 000000000000002a CS: 0033 SS: 002b

All '(podman)' processes seem to be stuck waiting on a unix socket for their peer.