[v6.1] WARNING in gid_table_release_one (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 02b72ccb5f9d Linux 6.1.138
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17bf6670580000
kernel config: https://syzkaller.appspot.com/x/.config?x=40498c8aeab367b8
dashboard link: https://syzkaller.appspot.com/bug?extid=dcf14b61f3b6e726a85a
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/741917d96f57/disk-02b72ccb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b5e0c69249ae/vmlinux-02b72ccb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/06bfb546fb37/bzImage-02b72ccb.xz

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

smc: removing ib device syz1
------------[ cut here ]------------
GID entry ref leak for dev syz1 index 2 ref=1
WARNING: CPU: 0 PID: 5239 at drivers/infiniband/core/cache.c:809 release_gid_table drivers/infiniband/core/cache.c:806 [inline]
WARNING: CPU: 0 PID: 5239 at drivers/infiniband/core/cache.c:809 gid_table_release_one+0x30f/0x490 drivers/infiniband/core/cache.c:886
Modules linked in:
CPU: 0 PID: 5239 Comm: kworker/u4:24 Not tainted 6.1.138-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
Workqueue: ib-unreg-wq ib_unregister_work
RIP: 0010:release_gid_table drivers/infiniband/core/cache.c:806 [inline]
RIP: 0010:gid_table_release_one+0x30f/0x490 drivers/infiniband/core/cache.c:886
Code: 03 48 b9 00 00 00 00 00 fc ff df 0f b6 04 08 84 c0 75 3c 41 8b 0e 48 c7 c7 a0 82 4c 8b 48 8b 74 24 20 44 89 fa e8 b1 8b e9 f9 <0f> 0b e9 14 ff ff ff 44 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c 1a ff
RSP: 0018:ffffc900057bfae8 EFLAGS: 00010246
RAX: 506c1436f7c44600 RBX: ffff88807984d4d8 RCX: ffff88807e399dc0
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: 1ffff1100f309a80 R08: dffffc0000000000 R09: fffff52000af7eed
R10: fffff52000af7eed R11: 1ffff92000af7eec R12: 1ffff1100f309a9b
R13: ffff88807984d400 R14: ffff888147fdc700 R15: 0000000000000002
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055b6197bffb8 CR3: 000000000c68e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ib_device_release+0xce/0x1b0 drivers/infiniband/core/device.c:498
device_release+0x92/0x1c0 drivers/base/core.c:-1
kobject_cleanup lib/kobject.c:681 [inline]
kobject_release lib/kobject.c:712 [inline]
kref_put include/linux/kref.h:65 [inline]
kobject_put+0x21d/0x460 lib/kobject.c:729
process_one_work+0x898/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1250 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.