From: syzbot <syzbot+221e213bf17f17e0d6cd@syzkaller.appspotmail.com>
To: jgg@ziepe.ca, leon@kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, yanjun.zhu@linux.dev,
zyjzyj2000@gmail.com
Subject: Re: [syzbot] [rdma?] WARNING in rxe_pool_cleanup
Date: Sat, 08 Mar 2025 04:01:23 -0800 [thread overview]
Message-ID: <67cc3193.050a0220.14db68.001e.GAE@google.com> (raw)
In-Reply-To: <00000000000086d0e406184c8e78@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 21e4543a2e2f Merge tag 'slab-for-6.14-rc5' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15db14b7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=2040405600e83619
dashboard link: https://syzkaller.appspot.com/bug?extid=221e213bf17f17e0d6cd
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14819878580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13db14b7980000
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-21e4543a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/65830427be5d/vmlinux-21e4543a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d0e255ba87f2/bzImage-21e4543a.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/cd82bec15deb/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=12dfaa64580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+221e213bf17f17e0d6cd@syzkaller.appspotmail.com
smc: removing ib device syz0
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5401 at drivers/infiniband/sw/rxe/rxe_pool.c:116 rxe_pool_cleanup+0x47/0x50 drivers/infiniband/sw/rxe/rxe_pool.c:116
Modules linked in:
CPU: 0 UID: 0 PID: 5401 Comm: syz-executor270 Not tainted 6.14.0-rc5-syzkaller-00214-g21e4543a2e2f #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:rxe_pool_cleanup+0x47/0x50 drivers/infiniband/sw/rxe/rxe_pool.c:116
Code: 00 00 fc ff df 80 3c 08 00 74 08 48 89 df e8 c0 6b 11 f9 48 83 3b 00 75 0b e8 b5 2f aa f8 5b c3 cc cc cc cc e8 aa 2f aa f8 90 <0f> 0b 90 5b c3 cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc9000d63f0e8 EFLAGS: 00010293
RAX: ffffffff8917af46 RBX: ffff88804bc69380 RCX: ffff8880002f8000
RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffff88804bc69300
RBP: 0000000000000002 R08: ffffffff88f02df3 R09: 1ffff1100978d0ee
R10: dffffc0000000000 R11: ffffffff8915c190 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff88804bc68658 R15: dffffc0000000000
FS: 00007fdbc26506c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000004bbba000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
rxe_dealloc+0x33/0x100 drivers/infiniband/sw/rxe/rxe.c:24
ib_dealloc_device+0x50/0x200 drivers/infiniband/core/device.c:647
__ib_unregister_device+0x366/0x3d0 drivers/infiniband/core/device.c:1520
ib_unregister_device_and_put+0xb9/0xf0 drivers/infiniband/core/device.c:1567
nldev_dellink+0x2c6/0x310 drivers/infiniband/core/nldev.c:1825
rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]
rdma_nl_rcv+0x6dd/0x9e0 drivers/infiniband/core/netlink.c:259
netlink_unicast_kernel net/netlink/af_netlink.c:1312 [inline]
netlink_unicast+0x7f6/0x990 net/netlink/af_netlink.c:1338
netlink_sendmsg+0x8de/0xcb0 net/netlink/af_netlink.c:1882
sock_sendmsg_nosec net/socket.c:718 [inline]
__sock_sendmsg+0x221/0x270 net/socket.c:733
____sys_sendmsg+0x53a/0x860 net/socket.c:2573
___sys_sendmsg net/socket.c:2627 [inline]
__sys_sendmsg+0x269/0x350 net/socket.c:2659
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fdbc26a2489
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 1a 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fdbc2650168 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007fdbc272f4c8 RCX: 00007fdbc26a2489
RDX: 0000000020000000 RSI: 00004000000002c0 RDI: 0000000000000005
RBP: 00007fdbc272f4c0 R08: 00007fdbc26506c0 R09: 0000000000000000
R10: 00007fdbc26506c0 R11: 0000000000000246 R12: 00007fdbc272f4cc
R13: 0000000000000006 R14: 00007ffd776089d0 R15: 00007ffd77608ab8
</TASK>
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
prev parent reply other threads:[~2025-03-08 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 2:22 [syzbot] [rdma?] WARNING in rxe_pool_cleanup syzbot
2025-02-07 5:45 ` syzbot
2025-03-08 18:03 ` Zhu Yanjun
2025-03-08 12:01 ` syzbot [this message]
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=67cc3193.050a0220.14db68.001e.GAE@google.com \
--to=syzbot+221e213bf17f17e0d6cd@syzkaller.appspotmail.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yanjun.zhu@linux.dev \
--cc=zyjzyj2000@gmail.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