[v6.1] WARNING in rxe_pool_cleanup

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0cbb5f65e52f Linux 6.1.128
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12dcc1b0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ddc0722618a3964e
dashboard link: https://syzkaller.appspot.com/bug?extid=8f049ad0f2f7833bf29b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c6d849a518b0/disk-0cbb5f65.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/76ad82aaf432/vmlinux-0cbb5f65.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5d4b74f07bf4/bzImage-0cbb5f65.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8f049a...@syzkaller.appspotmail.com

smc: removing ib device s z1
------------[ cut here ]------------
WARNING: CPU: 0 PID: 20988 at drivers/infiniband/sw/rxe/rxe_pool.c:116 rxe_pool_cleanup+0x3e/0x50
Modules linked in:
CPU: 0 PID: 20988 Comm: syz.2.3967 Not tainted 6.1.128-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
RIP: 0010:rxe_pool_cleanup+0x3e/0x50 drivers/infiniband/sw/rxe/rxe_pool.c:116
Code: 48 b9 00 00 00 00 00 fc ff df 80 3c 08 00 74 08 48 89 df e8 34 e6 d9 f9 48 83 3b 00 75 07 e8 39 53 82 f9 5b c3 e8 32 53 82 f9 <0f> 0b 5b c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 55 41 57 41
RSP: 0018:ffffc9000d17f278 EFLAGS: 00010246
RAX: ffffffff8808496e RBX: ffff888057319290 RCX: 0000000000080000
RDX: ffffc9002000b000 RSI: 000000000007ffff RDI: 0000000000080000
RBP: 000000000000000e R08: ffffffff87e20def R09: ffffed100ae630e9
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff888057318628 R15: dffffc0000000000
FS: 00007f8dc45c46c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9c8526ef98 CR3: 0000000026f5a000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
rxe_dealloc+0x2f/0x100 drivers/infiniband/sw/rxe/rxe.c:24
ib_dealloc_device+0x48/0x1f0 drivers/infiniband/core/device.c:657
__ib_unregister_device+0x111/0x170 drivers/infiniband/core/device.c:1492
ib_unregister_device_and_put+0xb2/0xe0 drivers/infiniband/core/device.c:1539
nldev_dellink+0x2b6/0x300 drivers/infiniband/core/nldev.c:1749
rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]
rdma_nl_rcv+0x6c4/0x9c0 drivers/infiniband/core/netlink.c:259
netlink_unicast_kernel net/netlink/af_netlink.c:1311 [inline]
netlink_unicast+0x7d8/0x970 net/netlink/af_netlink.c:1337
netlink_sendmsg+0xa26/0xd60 net/netlink/af_netlink.c:1859
sock_sendmsg_nosec net/socket.c:718 [inline]
__sock_sendmsg net/socket.c:730 [inline]
____sys_sendmsg+0x5a5/0x8f0 net/socket.c:2519
___sys_sendmsg net/socket.c:2573 [inline]
__sys_sendmsg+0x2a9/0x390 net/socket.c:2602
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f8dc378cde9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f8dc45c4038 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f8dc39a6160 RCX: 00007f8dc378cde9
RDX: 0000000000000840 RSI: 00002000000000c0 RDI: 0000000000000003
RBP: 00007f8dc380e2a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f8dc39a6160 R15: 00007ffef3ad4968
</TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup