From: syzbot <syzbot+list43aba7164f4c62811792@syzkaller.appspotmail.com>
To: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly block report (Jun 2025)
Date: Wed, 25 Jun 2025 22:36:28 -0700 [thread overview]
Message-ID: <685cdc5c.a00a0220.34b642.00ed.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, 3 new issues were detected and 1 were fixed.
In total, 37 issues are still open and 98 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 22870 Yes possible deadlock in blk_mq_update_nr_hw_queues
https://syzkaller.appspot.com/bug?extid=6279b273d888c2017726
<2> 20143 Yes possible deadlock in loop_set_status
https://syzkaller.appspot.com/bug?extid=9b145229d11aa73e4571
<3> 6151 Yes KMSAN: kernel-infoleak in filemap_read
https://syzkaller.appspot.com/bug?extid=905d785c4923bea2c1db
<4> 2574 Yes INFO: task hung in bdev_release
https://syzkaller.appspot.com/bug?extid=4da851837827326a7cd4
<5> 1680 Yes INFO: task hung in blkdev_fallocate
https://syzkaller.appspot.com/bug?extid=39b75c02b8be0a061bfc
<6> 706 Yes INFO: task hung in bdev_open
https://syzkaller.appspot.com/bug?extid=5c6179f2c4f1e111df11
<7> 594 No INFO: task hung in read_part_sector (2)
https://syzkaller.appspot.com/bug?extid=82de77d3f217960f087d
<8> 380 Yes possible deadlock in queue_requests_store
https://syzkaller.appspot.com/bug?extid=48928935f5008dde0a41
<9> 257 Yes possible deadlock in pcpu_alloc_noprof (2)
https://syzkaller.appspot.com/bug?extid=91771b3fb86ec2dd7227
<10> 157 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-06-26 5:36 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=685cdc5c.a00a0220.34b642.00ed.GAE@google.com \
--to=syzbot+list43aba7164f4c62811792@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.