From: syzbot <syzbot+b0da83a6c0e2e2bddbd4@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: [syzbot] [rdma?] WARNING in gid_table_release_one (3)
Date: Fri, 12 Sep 2025 14:44:32 -0700 [thread overview]
Message-ID: <68c49440.a70a0220.3543fc.003d.GAE@google.com> (raw)
In-Reply-To: <68232e7b.050a0220.f2294.09f6.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] [rdma?] WARNING in gid_table_release_one (3)
Author: yanjun.zhu@linux.dev
#syz test: https://github.com/zhuyj/linux.git
v6.17_fix_gid_table_release_one
On 9/12/25 2:43 PM, syzbot wrote:
>> #syz test:https://github.com/zhuyj/linux.git v6.17_fix_gid_table_release_one
> unknown command "test:https://github.com/zhuyj/linux.git"
>
>> On 9/12/25 2:20 PM, syzbot wrote:
>>> Hello,
>>>
>>> syzbot has tested the proposed patch but the reproducer is still triggering an issue:
>>> WARNING in gid_table_release_one
>>>
>>> WARNING: CPU: 1 PID: 1342 at drivers/infiniband/core/cache.c:809 release_gid_table drivers/infiniband/core/cache.c:806 [inline]
>>> WARNING: CPU: 1 PID: 1342 at drivers/infiniband/core/cache.c:809 gid_table_release_one+0x346/0x4d0 drivers/infiniband/core/cache.c:886
>>> Modules linked in:
>>> CPU: 1 UID: 0 PID: 1342 Comm: kworker/u8:7 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:806 [inline]
>>> RIP: 0010:gid_table_release_one+0x346/0x4d0 drivers/infiniband/core/cache.c:886
>>> Code: e8 03 48 b9 00 00 00 00 00 fc ff df 0f b6 04 08 84 c0 75 3d 41 8b 0e 48 c7 c7 00 46 71 8c 4c 89 e6 44 89 fa e8 3b a5 fa f8 90 <0f> 0b 90 90 e9 e3 fe ff ff 44 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c
>>> RSP: 0018:ffffc90004bff908 EFLAGS: 00010246
>>> RAX: 6115427e6ab01100 RBX: ffff88807855c2d8 RCX: ffff888027abbc00
>>> RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
>>> RBP: 1ffff1100f0ab85b R08: 0000000000000003 R09: 0000000000000004
>>> R10: dffffc0000000000 R11: fffffbfff1bfa24c R12: ffff8880206a4b40
>>> R13: ffff88807855c200 R14: ffff88801ffd5a00 R15: 0000000000000002
>>> FS: 0000000000000000(0000) GS:ffff888125d16000(0000) knlGS:0000000000000000
>>> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>>> CR2: 0000200000000240 CR3: 000000005e54a000 CR4: 00000000003526f0
>>> Call Trace:
>>> <TASK>
>>> ib_device_release+0xd2/0x1c0 drivers/infiniband/core/device.c:509
>>> device_release+0x99/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: e5320428 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=12829934580000
>>> 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.
next prev parent reply other threads:[~2025-09-12 21:44 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 11:35 syzbot
2025-05-14 8:54 ` Leon Romanovsky
2025-09-17 12:45 ` Jason Gunthorpe
2025-06-25 21:01 ` [syzbot] " syzbot
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
2025-09-12 20:50 ` Forwarded: " syzbot
2025-09-12 21:44 ` syzbot [this message]
2025-09-15 21:34 ` syzbot
2025-09-15 22:49 ` syzbot
2025-09-16 1:02 ` syzbot
2025-09-16 5:02 ` syzbot
2025-09-16 15:21 ` syzbot
2025-09-16 21:16 ` syzbot
2025-09-16 21:47 ` syzbot
2025-09-18 4:27 ` syzbot
2025-11-04 18:47 ` syzbot
2025-11-04 21:03 ` syzbot
2025-11-05 16:44 ` syzbot
2025-11-05 17:24 ` syzbot
2025-11-05 18:33 ` syzbot
2025-11-06 0:33 ` syzbot
2025-11-06 1:45 ` syzbot
2025-11-06 18:57 ` syzbot
2025-12-07 13:18 ` syzbot
2025-12-07 13:20 ` Forwarded: Fwd: " syzbot
2025-12-07 15:13 ` Forwarded: " syzbot
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=68c49440.a70a0220.3543fc.003d.GAE@google.com \
--to=syzbot+b0da83a6c0e2e2bddbd4@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®