From: syzbot <syzbot+list4a63d4f06484a1c63c1b@syzkaller.appspotmail.com>
To: agordeev@linux.ibm.com, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly s390 report (Jan 2025)
Date: Mon, 06 Jan 2025 02:01:27 -0800 [thread overview]
Message-ID: <677ba9f7.050a0220.a40f5.0008.GAE@google.com> (raw)
Hello s390 maintainers/developers,
This is a 31-day syzbot report for the s390 subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/s390
During the period, 1 new issues were detected and 0 were fixed.
In total, 7 issues are still open and 43 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 13861 Yes possible deadlock in smc_switch_to_fallback (2)
https://syzkaller.appspot.com/bug?extid=bef85a6996d1737c1a2f
<2> 2301 Yes possible deadlock in smc_vlan_by_tcpsk
https://syzkaller.appspot.com/bug?extid=c75d1de73d3b8b76272f
<3> 153 Yes general protection fault in smc_diag_dump_proto
https://syzkaller.appspot.com/bug?extid=f69bfae0a4eb29976e44
<4> 40 Yes possible deadlock in smc_release
https://syzkaller.appspot.com/bug?extid=621fd56ba002faba6392
<5> 39 Yes general protection fault in __smc_diag_dump (3)
https://syzkaller.appspot.com/bug?extid=271fed3ed6f24600c364
---
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-01-06 10:01 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=677ba9f7.050a0220.a40f5.0008.GAE@google.com \
--to=syzbot+list4a63d4f06484a1c63c1b@syzkaller.appspotmail.com \
--cc=agordeev@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@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