From: syzbot <syzbot+list16381c3f7f9f0890654e@syzkaller.appspotmail.com>
To: alibuda@linux.alibaba.com, dust.li@linux.alibaba.com,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-s390@vger.kernel.org, netdev@vger.kernel.org,
sidraya@linux.ibm.com, syzkaller-bugs@googlegroups.com,
wenjia@linux.ibm.com
Subject: [syzbot] Monthly smc report (Sep 2025)
Date: Thu, 18 Sep 2025 13:44:29 -0700 [thread overview]
Message-ID: <68cc6f2d.a00a0220.37dadf.000a.GAE@google.com> (raw)
Hello smc maintainers/developers,
This is a 31-day syzbot report for the smc subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/smc
During the period, 1 new issues were detected and 1 were fixed.
In total, 6 issues are still open and 46 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 484 Yes general protection fault in smc_diag_dump_proto
https://syzkaller.appspot.com/bug?extid=f69bfae0a4eb29976e44
<2> 128 Yes possible deadlock in smc_release
https://syzkaller.appspot.com/bug?extid=621fd56ba002faba6392
<3> 5 Yes general protection fault in __smc_diag_dump (4)
https://syzkaller.appspot.com/bug?extid=f775be4458668f7d220e
---
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-09-18 20:44 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=68cc6f2d.a00a0220.37dadf.000a.GAE@google.com \
--to=syzbot+list16381c3f7f9f0890654e@syzkaller.appspotmail.com \
--cc=alibuda@linux.alibaba.com \
--cc=dust.li@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sidraya@linux.ibm.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wenjia@linux.ibm.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