mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: syzbot
	<syzbot+list130c9052d10c27bfc9e9@syzkaller.appspotmail.com>,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Monthly rdma report (Jun 2025)
Date: Fri, 20 Jun 2025 08:12:48 -0700	[thread overview]
Message-ID: <a3781077-5f71-45e1-bd73-1a85d927fecd@linux.dev> (raw)
In-Reply-To: <68552aae.a00a0220.137b3.003f.GAE@google.com>

在 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?

The link should be: 
https://lore.kernel.org/all/6813a531.050a0220.14dd7d.0018.GAE@google.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@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-06-20 15:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20  9:32 syzbot
2025-06-20 15:12 ` Zhu Yanjun [this message]
2025-06-20 15:23   ` Zhu Yanjun
2025-06-20 15:56     ` Aleksandr Nogikh

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=a3781077-5f71-45e1-bd73-1a85d927fecd@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=syzbot+list130c9052d10c27bfc9e9@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

all inboxes | Powered by JetHome®