From: syzbot <syzbot+list82a918bf0af167b1c8dc@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly rdma report (Nov 2025)
Date: Sun, 23 Nov 2025 23:46:25 -0800 [thread overview]
Message-ID: <69240d51.a70a0220.d98e3.007e.GAE@google.com> (raw)
Hello rdma maintainers/developers,
This is a 31-day syzbot report for the rdma subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/rdma
During the period, 0 new issues were detected and 0 were fixed.
In total, 8 issues are still open and 66 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1145 No INFO: task hung in rdma_dev_change_netns
https://syzkaller.appspot.com/bug?extid=73c5eab674c7e1e7012e
<2> 579 Yes WARNING in rxe_pool_cleanup
https://syzkaller.appspot.com/bug?extid=221e213bf17f17e0d6cd
<3> 192 Yes WARNING in gid_table_release_one (3)
https://syzkaller.appspot.com/bug?extid=b0da83a6c0e2e2bddbd4
<4> 114 No INFO: task hung in rdma_dev_exit_net (6)
https://syzkaller.appspot.com/bug?extid=3658758f38a2f0f062e7
<5> 97 No INFO: task hung in add_one_compat_dev (3)
https://syzkaller.appspot.com/bug?extid=6dee15fdb0606ef7b6ba
<6> 8 Yes KMSAN: uninit-value in ib_nl_handle_ip_res_resp
https://syzkaller.appspot.com/bug?extid=938fcd548c303fe33c1a
---
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.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2025-11-24 7:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=69240d51.a70a0220.d98e3.007e.GAE@google.com \
--to=syzbot+list82a918bf0af167b1c8dc@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@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