From: syzbot <syzbot+list35c2a04b7be876f280f0@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly rdma report (Apr 2025)
Date: Thu, 03 Apr 2025 00:06:21 -0700 [thread overview]
Message-ID: <67ee336d.050a0220.9040b.0150.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 1 were fixed.
In total, 18 issues are still open and 63 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 25924 Yes possible deadlock in smc_switch_to_fallback (2)
https://syzkaller.appspot.com/bug?extid=bef85a6996d1737c1a2f
<2> 356 No INFO: task hung in rdma_dev_change_netns
https://syzkaller.appspot.com/bug?extid=73c5eab674c7e1e7012e
<3> 259 Yes general protection fault in smc_diag_dump_proto
https://syzkaller.appspot.com/bug?extid=f69bfae0a4eb29976e44
<4> 199 Yes WARNING in rxe_pool_cleanup
https://syzkaller.appspot.com/bug?extid=221e213bf17f17e0d6cd
<5> 91 Yes possible deadlock in sock_set_reuseaddr
https://syzkaller.appspot.com/bug?extid=af5682e4f50cd6bce838
<6> 70 No INFO: task hung in add_one_compat_dev (3)
https://syzkaller.appspot.com/bug?extid=6dee15fdb0606ef7b6ba
<7> 13 Yes KASAN: null-ptr-deref Read in smc_tcp_syn_recv_sock
https://syzkaller.appspot.com/bug?extid=827ae2bfb3a3529333e9
<8> 13 No possible deadlock in smc_shutdown (2)
https://syzkaller.appspot.com/bug?extid=3667d719a932ebc28119
---
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-04-03 7:06 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=67ee336d.050a0220.9040b.0150.GAE@google.com \
--to=syzbot+list35c2a04b7be876f280f0@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
all inboxes | Powered by JetHome®