[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANp29Y5yssN5p-QwyB=ci4HwY9EUSC0aKcAenU_CyXiu_zhxFA@mail.gmail.com>
Date: Fri, 20 Jun 2025 17:56:40 +0200
From: Aleksandr Nogikh <nogikh@...gle.com>
To: Zhu Yanjun <yanjun.zhu@...ux.dev>
Cc: syzbot <syzbot+list130c9052d10c27bfc9e9@...kaller.appspotmail.com>,
linux-kernel@...r.kernel.org, linux-rdma@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] Monthly rdma report (Jun 2025)
Hi,
On Fri, Jun 20, 2025 at 5:24 PM Zhu Yanjun <yanjun.zhu@...ux.dev> wrote:
>
>
>
> 在 2025/6/20 8:12, Zhu Yanjun 写道:
> > 在 2025/6/20 2:32, syzbot 写道:
> >> 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 65 have already been fixed.
> >>
> >> Some of the still happening issues:
> >>
> >> Ref Crashes Repro Title
> >> <1> 462 No INFO: task hung in rdma_dev_change_netns
> >> https://syzkaller.appspot.com/bug?
> >> extid=73c5eab674c7e1e7012e
> >> <2> 338 Yes WARNING in rxe_pool_cleanup
> >> https://syzkaller.appspot.com/bug?
> >> extid=221e213bf17f17e0d6cd
> >> <3> 72 No INFO: task hung in add_one_compat_dev (3)
> >> https://syzkaller.appspot.com/bug?
> >> extid=6dee15fdb0606ef7b6ba
> >> <4> 50 No INFO: task hung in rdma_dev_exit_net (6)
> >> https://syzkaller.appspot.com/bug?
> >> extid=3658758f38a2f0f062e7
> >> <5> 28 Yes WARNING in gid_table_release_one (3)
> >> https://syzkaller.appspot.com/bug?
> >> extid=b0da83a6c0e2e2bddbd4
> >> <6> 5 No WARNING in rxe_skb_tx_dtor
> >> https://syzkaller.appspot.com/bug?
> >> extid=8425ccfb599521edb153
> >
> > To this rxe_skb_tx_dtor problem, I think I have posted a fix. Do you
> > make tests with it?
In general, syzbot can test patches for the bugs it reported:
https://github.com/google/syzkaller/blob/master/docs/syzbot.md#testing-patches
But syzbot hasn't (yet) managed to find a reproducer for that specific
issue, so there's no way for the tool to test the candidate fix.
>
> Should I file an official commit to confirm if this problem is fixed or not?
>
> Yanjun.Zhu
>
> >
> > The link should be: https://lore.kernel.org/
> > all/6813a531.050a0220.14dd7d.0018.GAE@...gle.com/T/
> >
> > Best Regards,
> > Yanjun.Zhu
> >
> >>
> >> ---
> >> 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@...glegroups.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.
> >
>
> --
> Best Regards,
> Yanjun.Zhu
>
--
Aleksandr
Powered by blists - more mailing lists