mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [syzbot] [rdma?] WARNING in __rxe_cleanup
@ 2026-10-23 12:35 syzbot
  2026-10-24  3:31 ` Zhu Yanjun
  2026-11-19 21:03 ` syzbot
  0 siblings, 2 replies; 3+ messages in thread
From: syzbot @ 2026-10-23 12:35 UTC (permalink / raw)
  To: jgg, leon, linux-kernel, linux-rdma, syzkaller-bugs, zyjzyj2000

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [syzbot] [rdma?] WARNING in __rxe_cleanup
  2026-10-23 12:35 [syzbot] [rdma?] WARNING in __rxe_cleanup syzbot
@ 2026-10-24  3:31 ` Zhu Yanjun
  2026-11-19 21:03 ` syzbot
  1 sibling, 0 replies; 3+ messages in thread
From: Zhu Yanjun @ 2026-10-24  3:31 UTC (permalink / raw)
  To: syzbot, jgg, leon, linux-kernel, linux-rdma, syzkaller-bugs,
	zyjzyj2000, yanjun.zhu

在 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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [syzbot] [rdma?] WARNING in __rxe_cleanup
  2026-10-23 12:35 [syzbot] [rdma?] WARNING in __rxe_cleanup syzbot
  2026-10-24  3:31 ` Zhu Yanjun
@ 2026-11-19 21:03 ` syzbot
  1 sibling, 0 replies; 3+ messages in thread
From: syzbot @ 2026-11-19 21:03 UTC (permalink / raw)
  To: jgg, leon, linux-kernel, linux-rdma, syzkaller-bugs, yanjun.zhu,
	zyjzyj2000

syzbot has found a reproducer for the following issue on:

HEAD commit:    a041bdbe1f3a arm64: Drop stdint.h type overrides from asm/..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=14adccd5580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4e8e6c1701ad8af2
dashboard link: https://syzkaller.appspot.com/bug?extid=fef38133c495aeb48297
compiler:       Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
userspace arch: arm64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14f37403580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11d60153580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ed0e5cdd75d2/disk-a041bdbe.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/219ccd252cd7/vmlinux-a041bdbe.xz
kernel image: https://storage.googleapis.com/syzbot-assets/adb21ff27181/Image-a041bdbe.gz.xz

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

------------[ cut here ]------------
WARNING: drivers/infiniband/sw/rxe/rxe_pool.c:212 at __rxe_cleanup+0x244/0x28c drivers/infiniband/sw/rxe/rxe_pool.c:212, CPU#1: syz.0.17/4954
Modules linked in:
CPU: 1 UID: 0 PID: 4954 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : __rxe_cleanup+0x244/0x28c drivers/infiniband/sw/rxe/rxe_pool.c:212
lr : __rxe_cleanup+0x244/0x28c drivers/infiniband/sw/rxe/rxe_pool.c:212
sp : ffff800098747650
x29: ffff800098747650 x28: 1fffe0001b49bc03 x27: dfff800000000000
x26: ffff8000987476e0 x25: 00000000da70a250 x24: 0000000000000000
x23: dfff800000000000 x22: ffff0000d512d5b0 x21: ffff0000da70a250
x20: 0000000000000000 x19: ffff0000da70a250 x18: 1fffe000359d3e28
x17: 0000000000000003 x16: ffff8000898b7000 x15: ffff80008b586000
x14: 00000000005ab704 x13: 0000000000000001 x12: 0000000000000003
x11: 0000000000000000 x10: 0000000000000001 x9 : 0000000000000000
x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000008 x3 : ffff800084641254
x2 : 0000000000000000 x1 : ffff0000d15d0000 x0 : 0000000000000000
Call trace:
 __rxe_cleanup+0x244/0x28c drivers/infiniband/sw/rxe/rxe_pool.c:212 (P)
 rxe_destroy_qp+0x80/0x270 drivers/infiniband/sw/rxe/rxe_verbs.c:661
 ib_destroy_qp_user+0x2d8/0x548 drivers/infiniband/core/verbs.c:2182
 uverbs_free_qp+0xdc/0x188 drivers/infiniband/core/uverbs_std_types_qp.c:34
 destroy_hw_idr_uobject+0x90/0x120 drivers/infiniband/core/rdma_core.c:579
 uverbs_destroy_uobject+0x23c/0x4f4 drivers/infiniband/core/rdma_core.c:172
 __uverbs_cleanup_ufile+0x1e8/0x334 drivers/infiniband/core/rdma_core.c:959
 uverbs_destroy_ufile_hw+0x88/0x210 drivers/infiniband/core/uverbs_main.c:1003
 ib_uverbs_close+0x54/0x200 drivers/infiniband/core/uverbs_main.c:1018
 __fput+0x338/0x74c fs/file_table.c:512
 ____fput+0x20/0x30 fs/file_table.c:541
 task_work_run+0x1cc/0x25c kernel/task_work.c:233
 exit_task_work include/linux/task_work.h:40 [inline]
 do_exit+0x570/0x1a64 kernel/exit.c:980
 do_group_exit+0x198/0x238 kernel/exit.c:1123
 __do_sys_exit_group kernel/exit.c:1134 [inline]
 __se_sys_exit_group kernel/exit.c:1132 [inline]
 pid_child_should_wake+0x0/0x104 kernel/exit.c:1132
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121
 do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140
 el0_svc+0x60/0x1d8 arch/arm64/kernel/entry-common.c:797
 el0t_64_sync_handler+0x44/0x104 arch/arm64/kernel/entry-common.c:816
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:606
irq event stamp: 2998
hardirqs last  enabled at (2997): [<ffff80008697a52c>] __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:219 [inline]
hardirqs last  enabled at (2997): [<ffff80008697a52c>] _raw_spin_unlock_irq+0x30/0x80 kernel/locking/spinlock.c:229
hardirqs last disabled at (2998): [<ffff8000869540f0>] el1_brk64+0x20/0x54 arch/arm64/kernel/entry-common.c:484
softirqs last  enabled at (2638): [<ffff8000800204f4>] __do_softirq+0x14/0x20 kernel/softirq.c:703
softirqs last disabled at (1173): [<ffff8000800204f4>] __do_softirq+0x14/0x20 kernel/softirq.c:703
---[ end trace 0000000000000000 ]---
rxe0: qp#17 rxe_destroy_qp: cleanup failed, err = -110

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-11-19 21:03 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-10-23 12:35 [syzbot] [rdma?] WARNING in __rxe_cleanup syzbot
2026-10-24  3:31 ` Zhu Yanjun
2026-11-19 21:03 ` syzbot

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®