[syzbot] [rdma?] WARNING in __rxe_cleanup

[syzbot] [rdma?] WARNING in __rxe_cleanup

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    c03c1a14507d Linux 7.3
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1796a621580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c4b098695335c89f
dashboard link: https://syzkaller.appspot.com/bug?extid=fef38133c495aeb48297
compiler:       Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c9d4a36731a6/disk-c03c1a14.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3c00e4e185bb/vmlinux-c03c1a14.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1f95d3156291/bzImage-c03c1a14.xz

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

------------[ cut here ]------------
!ret
WARNING: drivers/infiniband/sw/rxe/rxe_pool.c:212 at __rxe_cleanup+0x311/0x350 drivers/infiniband/sw/rxe/rxe_pool.c:212, CPU#0: kworker/u8:9/3389
Modules linked in:
CPU: 0 UID: 0 PID: 3389 Comm: kworker/u8:9 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2026
Workqueue: krds_cp_wq#0/0 rds_shutdown_worker
RIP: 0010:__rxe_cleanup+0x311/0x350 drivers/infiniband/sw/rxe/rxe_pool.c:212
Code: f7 be 03 00 00 00 e8 7e 15 e8 fb 40 84 ed 0f 85 26 fe ff ff e9 5b fe ff ff e8 5b 89 cf f8 90 0f 0b 90 eb 09 e8 50 89 cf f8 90 <0f> 0b 90 41 be 92 ff ff ff e9 47 ff ff ff 44 89 f1 80 e1 07 80 c1
RSP: 0018:ffffc9000f2ff6d0 EFLAGS: 00010293
RAX: ffffffff88f888b0 RBX: ffff88807f162250 RCX: ffff888034160000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffff917a757f R09: 1ffffffff22f4eaf
R10: dffffc0000000000 R11: fffffbfff22f4eb0 R12: ffff88807e7615a0
R13: 00000000ffffffff R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff888123abf000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffd5380382c CR3: 000000003558f000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 rxe_destroy_qp+0x74/0x270 drivers/infiniband/sw/rxe/rxe_verbs.c:661
 ib_destroy_qp_user+0x354/0x5a0 drivers/infiniband/core/verbs.c:2182
 ib_destroy_qp include/rdma/ib_verbs.h:4103 [inline]
 rdma_destroy_qp+0xd0/0x250 drivers/infiniband/core/cma.c:1170
 rds_ib_conn_path_shutdown+0x9bd/0x1820 net/rds/ib_cm.c:1113
 rds_conn_shutdown+0x477/0xb20 net/rds/connection.c:440
 process_one_work kernel/workqueue.c:3396 [inline]
 process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3479
 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3560
 kthread+0x38b/0x480 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 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 syzkaller@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

Re: [syzbot] [rdma?] WARNING in __rxe_cleanup

[Zhu Yanjun]

在 2026/10/23 5:35, syzbot 写道:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    c03c1a14507d Linux 7.3
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1796a621580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=c4b098695335c89f
> dashboard link: https://syzkaller.appspot.com/bug?extid=fef38133c495aeb48297
> compiler:       Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
> 
> Unfortunately, I don't have any reproducer for this issue yet.
> 
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/c9d4a36731a6/disk-c03c1a14.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/3c00e4e185bb/vmlinux-c03c1a14.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/1f95d3156291/bzImage-c03c1a14.xz
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+fef38133c495aeb48297@syzkaller.appspotmail.com
> 
> ------------[ cut here ]------------
> !ret
> WARNING: drivers/infiniband/sw/rxe/rxe_pool.c:212 at __rxe_cleanup+0x311/0x350 drivers/infiniband/sw/rxe/rxe_pool.c:212, CPU#0: kworker/u8:9/3389
> Modules linked in:
> CPU: 0 UID: 0 PID: 3389 Comm: kworker/u8:9 Tainted: G             L      syzkaller #0 PREEMPT(full)
> Tainted: [L]=SOFTLOCKUP
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2026
> Workqueue: krds_cp_wq#0/0 rds_shutdown_worker
> RIP: 0010:__rxe_cleanup+0x311/0x350 drivers/infiniband/sw/rxe/rxe_pool.c:212

Hi,

Looking at the stack trace and rxe_pool.c:212:

203     if (sleepable) {
204         if (!completion_done(&elem->complete)) {
205             ret = wait_for_completion_timeout(&elem->complete,
206                     msecs_to_jiffies(50000));
207
208             /* Shouldn't happen. There are still references to
209              * the object but, rather than deadlock, free the
210              * object or pass back to rdma-core.
211              */
212             if (WARN_ON(!ret))
213                 err = -ETIMEDOUT;
214         }
215     }

The WARNING triggers because __rxe_cleanup() timed out waiting 50s for 
the QP reference count to drop to zero during destruction.

This indicates an unreleased QP reference leak on the upper layer side 
(RDS) during connection teardown (rds_shutdown_worker -> 
rds_ib_conn_path_shutdown).

While RXE forces object cleanup after 50 seconds to prevent a deadlock, 
the root cause lies in net/rds failing to drop all held QP references 
prior to calling rdma_destroy_qp(). This needs to be addressed on the 
RDS layer.

Thanks.

Yanjun Zhu

> Code: f7 be 03 00 00 00 e8 7e 15 e8 fb 40 84 ed 0f 85 26 fe ff ff e9 5b fe ff ff e8 5b 89 cf f8 90 0f 0b 90 eb 09 e8 50 89 cf f8 90 <0f> 0b 90 41 be 92 ff ff ff e9 47 ff ff ff 44 89 f1 80 e1 07 80 c1
> RSP: 0018:ffffc9000f2ff6d0 EFLAGS: 00010293
> RAX: ffffffff88f888b0 RBX: ffff88807f162250 RCX: ffff888034160000
> RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
> RBP: 0000000000000001 R08: ffffffff917a757f R09: 1ffffffff22f4eaf
> R10: dffffc0000000000 R11: fffffbfff22f4eb0 R12: ffff88807e7615a0
> R13: 00000000ffffffff R14: 0000000000000000 R15: 0000000000000000
> FS:  0000000000000000(0000) GS:ffff888123abf000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007ffd5380382c CR3: 000000003558f000 CR4: 0000000000350ef0
> Call Trace:
>   <TASK>
>   rxe_destroy_qp+0x74/0x270 drivers/infiniband/sw/rxe/rxe_verbs.c:661
>   ib_destroy_qp_user+0x354/0x5a0 drivers/infiniband/core/verbs.c:2182
>   ib_destroy_qp include/rdma/ib_verbs.h:4103 [inline]
>   rdma_destroy_qp+0xd0/0x250 drivers/infiniband/core/cma.c:1170
>   rds_ib_conn_path_shutdown+0x9bd/0x1820 net/rds/ib_cm.c:1113
>   rds_conn_shutdown+0x477/0xb20 net/rds/connection.c:440
>   process_one_work kernel/workqueue.c:3396 [inline]
>   process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3479
>   worker_thread+0xa47/0xfb0 kernel/workqueue.c:3560
>   kthread+0x38b/0x480 kernel/kthread.c:436
>   ret_from_fork+0x514/0xb70 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 syzkaller@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