From: syzbot <syzbot+list863428c2ecf6cf92766a@syzkaller.appspotmail.com>
To: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly block report (Jun 2026)
Date: Wed, 03 Jun 2026 21:32:25 -0700 [thread overview]
Message-ID: <6a20ffd9.323e8352.3b6a81.004a.GAE@google.com> (raw)
Hello block maintainers/developers,
This is a 31-day syzbot report for the block subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/block
During the period, 0 new issues were detected and 0 were fixed.
In total, 17 issues are still open and 112 have already been fixed.
There are also 26 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 9088 Yes KMSAN: kernel-infoleak in filemap_read
https://syzkaller.appspot.com/bug?extid=905d785c4923bea2c1db
<2> 1729 Yes INFO: task hung in blkdev_fallocate
https://syzkaller.appspot.com/bug?extid=39b75c02b8be0a061bfc
<3> 215 Yes general protection fault in rtlock_slowlock_locked
https://syzkaller.appspot.com/bug?extid=08df3e4c9b304b37cb04
<4> 60724 Yes possible deadlock in __submit_bio
https://syzkaller.appspot.com/bug?extid=949ae54e95a2fab4cbb4
<5> 69 Yes INFO: task hung in blk_trace_remove (2)
https://syzkaller.appspot.com/bug?extid=2373f6be3e6de4f92562
<6> 18 No KASAN: slab-out-of-bounds Read in blk_mq_free_rqs
https://syzkaller.appspot.com/bug?extid=e90526cab23b9efcd03c
---
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:[~2026-06-04 4:32 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=6a20ffd9.323e8352.3b6a81.004a.GAE@google.com \
--to=syzbot+list863428c2ecf6cf92766a@syzkaller.appspotmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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