From: "yanjun.zhu" <yanjun.zhu@linux.dev>
To: syzbot
<syzbot+list0ee54e0d9d6647c72420@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Monthly rdma report (Oct 2025)
Date: Thu, 23 Oct 2025 12:05:49 -0700 [thread overview]
Message-ID: <9fdc4b67-71dc-4a03-a852-bb7b0c8fd04b@linux.dev> (raw)
In-Reply-To: <68f9d8a1.050a0220.346f24.0070.GAE@google.com>
On 10/23/25 12:26 AM, syzbot wrote:
> 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, 1 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> 969 No INFO: task hung in rdma_dev_change_netns
> https://syzkaller.appspot.com/bug?extid=73c5eab674c7e1e7012e
> <2> 546 Yes WARNING in rxe_pool_cleanup
> https://syzkaller.appspot.com/bug?extid=221e213bf17f17e0d6cd
> <3> 100 No INFO: task hung in rdma_dev_exit_net (6)
> https://syzkaller.appspot.com/bug?extid=3658758f38a2f0f062e7
> <4> 94 No INFO: task hung in add_one_compat_dev (3)
> https://syzkaller.appspot.com/bug?extid=6dee15fdb0606ef7b6ba
> <5> 89 Yes WARNING in gid_table_release_one (3)
> https://syzkaller.appspot.com/bug?extid=b0da83a6c0e2e2bddbd4
About this problem ("WARNING in gid_table_release_one (3)"), I have a
commit that can solve this problem. I will send it out for code review soon.
Yanjun.Zhu
> <6> 5 Yes KASAN: slab-use-after-free Read in ucma_create_uevent
> https://syzkaller.appspot.com/bug?extid=a6ffe86390c8a6afc818
>
> ---
> 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.
prev parent reply other threads:[~2025-10-23 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 7:26 [syzbot] Monthly rdma report (Oct 2025) syzbot
2025-10-23 19:05 ` yanjun.zhu [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=9fdc4b67-71dc-4a03-a852-bb7b0c8fd04b@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=syzbot+list0ee54e0d9d6647c72420@syzkaller.appspotmail.com \
--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;
as well as URLs for NNTP newsgroup(s).