From: syzbot <syzbot+b0da83a6c0e2e2bddbd4@syzkaller.appspotmail.com>
To: jgg@ziepe.ca, leon@kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, yanjun.zhu@linux.dev
Subject: Re: [syzbot] [rdma?] WARNING in gid_table_release_one (3)
Date: Wed, 05 Nov 2025 20:02:03 -0800 [thread overview]
Message-ID: <690c1dbb.050a0220.3d0d33.00df.GAE@google.com> (raw)
In-Reply-To: <81fedfc2-8e6e-44f3-94d4-2c694c759ded@linux.dev>
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=353, state: 3
WARNING: CPU: 1 PID: 36 at drivers/infiniband/core/cache.c:817 release_gid_table drivers/infiniband/core/cache.c:814 [inline]
WARNING: CPU: 1 PID: 36 at drivers/infiniband/core/cache.c:817 gid_table_release_one+0x39e/0x570 drivers/infiniband/core/cache.c:894
Modules linked in:
CPU: 1 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 10/02/2025
Workqueue: ib-unreg-wq ib_unregister_work
RIP: 0010:release_gid_table drivers/infiniband/core/cache.c:814 [inline]
RIP: 0010:gid_table_release_one+0x39e/0x570 drivers/infiniband/core/cache.c:894
Code: 04 28 84 c0 0f 85 9d 00 00 00 45 8b 06 48 c7 c7 60 7c 2b 8c 48 8b 74 24 28 4c 8b 74 24 08 44 89 f2 44 89 e1 e8 83 e9 35 f9 90 <0f> 0b 90 90 e9 c5 fe ff ff e8 64 7e 72 f9 4c 8b 64 24 40 4c 89 e0
RSP: 0018:ffffc90000ac7900 EFLAGS: 00010246
RAX: d89947cea50d0900 RBX: ffff888076c960d8 RCX: ffff8881436c9e40
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: ffff888076c96000 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffffbfff1b7a678 R12: 0000000000000161
R13: dffffc0000000000 R14: 0000000000000002 R15: 1ffff1100ed92c1b
FS: 0000000000000000(0000) GS:ffff88812646a000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9b2bf056c0 CR3: 000000000db38000 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:3263 [inline]
process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3346
worker_thread+0x8a0/0xda0 kernel/workqueue.c:3427
kthread+0x711/0x8a0 kernel/kthread.c:463
ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Tested on:
commit: e365ec00 RDMA/core: Fix WARNING in gid_table_release_one
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=17a24a92580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2c614fa9e6f5bdc1
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.
next parent reply other threads:[~2025-11-06 4:02 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <81fedfc2-8e6e-44f3-94d4-2c694c759ded@linux.dev>
2025-11-06 4:02 ` syzbot [this message]
[not found] <1d5af932-89da-4492-b2b3-623783f0629f@nvidia.com>
2025-12-07 16:50 ` [syzbot] [rdma?] WARNING in gid_table_release_one (3) syzbot
[not found] <b40caa64-c06d-4b9d-bb0b-351d2858ee63@nvidia.com>
2025-12-07 14:22 ` syzbot
[not found] <dcc6491f-5f67-468b-a21a-90071719fa4b@nvidia.com>
2025-12-07 13:54 ` syzbot
[not found] <ffdab397-0096-4946-a7d5-073300cc34a3@linux.dev>
2025-11-06 21:02 ` syzbot
2025-11-06 21:08 ` Yanjun.Zhu
[not found] <38f2a630-7edc-4e9b-b5aa-3e983d67d024@linux.dev>
2025-11-06 1:11 ` syzbot
[not found] <d8cba3c4-117b-4e7c-a442-d38d5289680f@linux.dev>
2025-11-05 19:36 ` syzbot
[not found] <c2d8fc24-08a7-47fe-8f68-cc9bbe6c55a4@linux.dev>
2025-11-05 18:45 ` syzbot
[not found] <185e135e-0e17-4ef8-91a2-15e69897cd01@linux.dev>
2025-11-05 17:06 ` syzbot
2025-11-05 17:14 ` Jason Gunthorpe
2025-11-05 17:24 ` Yanjun.Zhu
2025-11-05 18:50 ` Leon Romanovsky
2025-11-05 20:10 ` Yanjun.Zhu
2025-11-06 0:44 ` Yanjun.Zhu
[not found] <198ed0eb-2451-4651-b723-a506e3cf853b@linux.dev>
2025-11-04 23:50 ` syzbot
[not found] <f5a387d4-eae3-4932-b170-37ff38ebe78d@linux.dev>
2025-11-04 23:22 ` syzbot
[not found] <b0988506-dbc6-4d28-8f19-9c50bdc44f84@linux.dev>
2025-09-18 6:13 ` syzbot
[not found] <689cd5e4-1ebe-4b81-8036-68393d61f4ce@linux.dev>
2025-09-16 22:21 ` syzbot
[not found] <295acd4d-1f40-455a-9d2f-27393cd047bd@linux.dev>
2025-09-16 21:39 ` syzbot
[not found] <bc6d2cd1-39a3-4b95-b8b1-92fecf28679d@linux.dev>
2025-09-16 15:48 ` syzbot
2025-09-16 16:12 ` Yanjun.Zhu
[not found] <a3dcd664-b39c-47ff-a61c-f834ba130a16@linux.dev>
2025-09-16 5:59 ` syzbot
[not found] <6aed82d8-8e65-402d-909e-b8cfbfbb41e4@linux.dev>
2025-09-16 2:10 ` syzbot
[not found] <d61c07c8-c5c1-4cfe-ad23-d972eaff8b9b@linux.dev>
2025-09-16 1:12 ` syzbot
[not found] <e50a6a79-6c0c-4313-a09e-a69d8456b202@linux.dev>
2025-09-15 22:14 ` syzbot
[not found] <7d02a204-fcf6-42c5-b9ad-b7238b9c703b@linux.dev>
2025-09-15 21:14 ` syzbot
[not found] <dfb7c3c3-dba2-4c99-9347-50715e652c59@linux.dev>
2025-09-15 20:55 ` syzbot
[not found] <1ea1efd9-4c9d-4432-82b7-f8998bd4e421@linux.dev>
2025-09-15 19:39 ` syzbot
[not found] <b06c5a01-839f-47bf-9530-705ec838fcbe@linux.dev>
2025-09-15 19:16 ` syzbot
[not found] <5fb34b0f-435e-4584-abe0-bbf7839b44df@linux.dev>
2025-09-15 19:07 ` syzbot
[not found] <b678b916-ad9f-4845-91b5-2e5d1f79fe24@linux.dev>
2025-09-12 22:04 ` syzbot
[not found] <19d2990f-ba92-4fef-891d-26baf03afe18@linux.dev>
2025-09-12 21:43 ` syzbot
[not found] <c9778714-2966-4b61-b371-9d831bd2492e@linux.dev>
2025-09-12 21:20 ` syzbot
2025-05-13 11:35 syzbot
2025-05-14 8:54 ` Leon Romanovsky
2025-09-17 12:45 ` Jason Gunthorpe
2025-09-11 15:34 ` syzbot
2025-09-12 3:39 ` Hillf Danton
2025-09-12 4:05 ` syzbot
2025-09-12 8:33 ` Hillf Danton
2025-09-12 8:36 ` syzbot
2025-09-12 9:42 ` Hillf Danton
2025-09-12 13:23 ` syzbot
2025-09-13 1:25 ` Hillf Danton
2025-09-13 2:48 ` syzbot
2025-09-13 7:25 ` Hillf Danton
2025-09-13 8:06 ` syzbot
2025-09-16 16:15 ` yanjun.zhu
2025-09-12 4:42 ` syzbot
2025-09-12 19:38 ` yanjun.zhu
2025-09-12 20:01 ` Yanjun.Zhu
2025-09-12 22:33 ` Yanjun.Zhu
2025-09-12 22:55 ` Yanjun.Zhu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=690c1dbb.050a0220.3d0d33.00df.GAE@google.com \
--to=syzbot+b0da83a6c0e2e2bddbd4@syzkaller.appspotmail.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yanjun.zhu@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.