[syzbot] [rdma?] WARNING in ib_cq_pool_cleanup

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 73e3f0710014 Merge tag 'nfs-for-7.3-1' of git://git.linux-..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12977415580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c2d3e2a7997c1d5c
dashboard link: https://syzkaller.appspot.com/bug?extid=d396918a29afb8543e1c
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/725c76492ae5/disk-73e3f071.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b4b32ef07d3c/vmlinux-73e3f071.xz
kernel image: https://storage.googleapis.com/syzbot-assets/afd59682ac03/bzImage-73e3f071.xz

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

smbdirect: ib_dev[syz2] removed
------------[ cut here ]------------
cq->cqe_used
WARNING: drivers/infiniband/core/cq.c:370 at ib_cq_pool_cleanup+0x248/0x370 drivers/infiniband/core/cq.c:370, CPU#1: kworker/u8:22/17817
Modules linked in:
CPU: 1 UID: 0 PID: 17817 Comm: kworker/u8:22 Tainted: G L syzkaller #0 PREEMPT(full)
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
Workqueue: ib-unreg-wq ib_unregister_work
RIP: 0010:ib_cq_pool_cleanup+0x248/0x370 drivers/infiniband/core/cq.c:370
Code: 41 f9 41 83 fe 03 0f 85 01 fe ff ff e8 21 92 41 f9 48 83 c4 20 5b 5d 41 5c 41 5d 41 5e 41 5f e9 fe b1 06 03 e8 09 92 41 f9 90 <0f> 0b 90 eb 84 e8 3e 76 b4 f9 e9 67 ff ff ff 48 8b 34 24 48 c7 c7
RSP: 0018:ffffc90004bcfac8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: dffffc0000000000 RCX: 0000000000000000
RDX: ffff88802e53a580 RSI: ffffffff88ca43e7 RDI: ffff88802e53a580
RBP: ffff888028e1c000 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000804 R11: 0000000000000000 R12: ffff888058b09840
R13: ffff88807d614ed0 R14: 0000000000000804 R15: ffff888058b09800
FS: 0000000000000000(0000) GS:ffff888123c6b000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007efff0e27dac CR3: 000000005a096000 CR4: 00000000003526f0
Call Trace:
<TASK>
disable_device+0x161/0x280 drivers/infiniband/core/device.c:1328
__ib_unregister_device+0x2b4/0x480 drivers/infiniband/core/device.c:1571
ib_unregister_work+0x19/0x30 drivers/infiniband/core/device.c:1683
process_one_work+0xac7/0x1b10 kernel/workqueue.c:3387
process_scheduled_works kernel/workqueue.c:3470 [inline]
worker_thread+0x5ef/0xe50 kernel/workqueue.c:3551
kthread+0x373/0x450 kernel/kthread.c:436
ret_from_fork+0x730/0xd60 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</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