From: syzbot <syzbot+liste73e8cca2b92b2455106@syzkaller.appspotmail.com>
To: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly block report (Sep 2025)
Date: Sat, 27 Sep 2025 13:43:31 -0700 [thread overview]
Message-ID: <68d84c73.a00a0220.102ee.001a.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, 1 new issues were detected and 0 were fixed.
In total, 44 issues are still open and 104 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 44250 Yes possible deadlock in blk_mq_update_nr_hw_queues
https://syzkaller.appspot.com/bug?extid=6279b273d888c2017726
<2> 43987 Yes possible deadlock in __del_gendisk
https://syzkaller.appspot.com/bug?extid=2e9e529ac0b319316453
<3> 7133 Yes KMSAN: kernel-infoleak in filemap_read
https://syzkaller.appspot.com/bug?extid=905d785c4923bea2c1db
<4> 3286 No INFO: task hung in read_part_sector (2)
https://syzkaller.appspot.com/bug?extid=82de77d3f217960f087d
<5> 2746 Yes BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! (7)
https://syzkaller.appspot.com/bug?extid=74f79df25c37437e4d5a
<6> 2614 Yes INFO: task hung in bdev_release
https://syzkaller.appspot.com/bug?extid=4da851837827326a7cd4
<7> 1688 Yes INFO: task hung in blkdev_fallocate
https://syzkaller.appspot.com/bug?extid=39b75c02b8be0a061bfc
<8> 1586 Yes INFO: task hung in bdev_open
https://syzkaller.appspot.com/bug?extid=5c6179f2c4f1e111df11
<9> 1007 Yes INFO: task hung in sync_bdevs (3)
https://syzkaller.appspot.com/bug?extid=97bc0b256218ed6df337
<10> 606 Yes possible deadlock in elevator_change
https://syzkaller.appspot.com/bug?extid=ccae337393ac17091c34
---
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-27 20:43 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=68d84c73.a00a0220.102ee.001a.GAE@google.com \
--to=syzbot+liste73e8cca2b92b2455106@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