linux-kernel - Re: [syzbot] [rdma?] WARNING in gid_table_release

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <68c8fca8.050a0220.3c6139.0d2b.GAE@google.com>
Date: Mon, 15 Sep 2025 22:59:04 -0700
From: syzbot <syzbot+b0da83a6c0e2e2bddbd4@...kaller.appspotmail.com>
To: jgg@...pe.ca, leon@...nel.org, linux-kernel@...r.kernel.org, 
	syzkaller-bugs@...glegroups.com, yanjun.zhu@...ux.dev
Subject: Re: [syzbot] [rdma?] WARNING in gid_table_release_one (3)

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in gid_table_release_one

------------[ cut here ]------------
GID entry ref leak for dev syz1 index 2 ref=391, state: 3
WARNING: CPU: 0 PID: 36 at drivers/infiniband/core/cache.c:813 release_gid_table drivers/infiniband/core/cache.c:810 [inline]
WARNING: CPU: 0 PID: 36 at drivers/infiniband/core/cache.c:813 gid_table_release_one+0x34e/0x4f0 drivers/infiniband/core/cache.c:890
Modules linked in:
CPU: 0 UID: 0 PID: 36 Comm: kworker/u8:2 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Workqueue: ib-unreg-wq ib_unregister_work
RIP: 0010:release_gid_table drivers/infiniband/core/cache.c:810 [inline]
RIP: 0010:gid_table_release_one+0x34e/0x4f0 drivers/infiniband/core/cache.c:890
Code: 4c 89 f0 48 c1 e8 03 42 0f b6 04 20 84 c0 75 64 45 8b 06 48 c7 c7 60 4b 71 8c 48 8b 74 24 20 44 89 fa 89 e9 e8 13 81 fa f8 90 <0f> 0b 90 90 e9 ab fe ff ff 44 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c
RSP: 0018:ffffc90000ac78f8 EFLAGS: 00010246
RAX: 4a34fa8552892100 RBX: ffff888031fba0d8 RCX: ffff88801d6f3c00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: 0000000000000187 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffffbfff1bfa24c R12: dffffc0000000000
R13: ffff888031fba000 R14: ffff8880744f8990 R15: 0000000000000002
FS:  0000000000000000(0000) GS:ffff888125c16000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f44957d5fa4 CR3: 000000002849e000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 ib_device_release+0xd2/0x1c0 drivers/infiniband/core/device.c:509
 device_release+0x9c/0x1c0 drivers/base/core.c:-1
 kobject_cleanup lib/kobject.c:689 [inline]
 kobject_release lib/kobject.c:720 [inline]
 kref_put include/linux/kref.h:65 [inline]
 kobject_put+0x22b/0x480 lib/kobject.c:737
 process_one_work kernel/workqueue.c:3236 [inline]
 process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3319
 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3400
 kthread+0x70e/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>


Tested on:

commit:         067ce8f1 RDMA/rxe: Add logs to find out the root cause
git tree:       https://github.com/zhuyj/linux.git v6.17_fix_gid_table_release_one
console output: https://syzkaller.appspot.com/x/log.txt?x=16304e42580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4239c29711f936f
dashboard link: https://syzkaller.appspot.com/bug?extid=b0da83a6c0e2e2bddbd4
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

Note: no patches were applied.