From: syzbot <syzbot+list1913a7ecb8f6c20c529b@syzkaller.appspotmail.com>
To: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly block report (Nov 2026)
Date: Fri, 06 Nov 2026 20:33:40 -0800 [thread overview]
Message-ID: <6aeeaa24.1da6ca5c.10a313.0000.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 2 were fixed.
In total, 30 issues are still open and 124 have already been fixed.
There are also 34 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 4342 No general protection fault in lo_rw_aio
https://syzkaller.appspot.com/bug?extid=cd8a9a308e879a4e2c28
<2> 2419 Yes possible deadlock in blkg_conf_prep
https://syzkaller.appspot.com/bug?extid=144a1c0e22e53a08ef5a
<3> 1749 Yes INFO: task hung in blkdev_fallocate
https://syzkaller.appspot.com/bug?extid=39b75c02b8be0a061bfc
<4> 323 Yes INFO: task hung in __rq_qos_throttle (2)
https://syzkaller.appspot.com/bug?extid=53706c567afab5131044
<5> 219 Yes general protection fault in rtlock_slowlock_locked
https://syzkaller.appspot.com/bug?extid=08df3e4c9b304b37cb04
<6> 69 Yes BUG: unable to handle kernel paging request in blk_mq_complete_request_remote
https://syzkaller.appspot.com/bug?extid=2e3bf0bd49acd9b21d4b
<7> 34 No WARNING in blk_mq_dispatch_rq_list
https://syzkaller.appspot.com/bug?extid=49b69d460fb5134ee1d7
<8> 31 Yes BUG: corrupted list in blk_mq_request_bypass_insert
https://syzkaller.appspot.com/bug?extid=f4353e96f7004ae5a09e
<9> 5 Yes WARNING: lock held when returning to user space in blk_throtl_init
https://syzkaller.appspot.com/bug?extid=1eb53c83ab8b0a0302a6
<10> 3348 Yes WARNING in blk_mq_free_tag_set
https://syzkaller.appspot.com/bug?extid=02b37e31e64ea5cb6d29
---
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-11-07 4:33 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=6aeeaa24.1da6ca5c.10a313.0000.GAE@google.com \
--to=syzbot+list1913a7ecb8f6c20c529b@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.