From: syzbot <syzbot+listcaaffe0cc9b9e6b9b16d@syzkaller.appspotmail.com>
To: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly block report (Mar 2024)
Date: Tue, 12 Mar 2024 02:29:26 -0700 [thread overview]
Message-ID: <0000000000005570bc0613734b42@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, 20 issues are still open and 92 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1396 Yes KMSAN: kernel-infoleak in filemap_read
https://syzkaller.appspot.com/bug?extid=905d785c4923bea2c1db
<2> 201 Yes INFO: task hung in blkdev_fallocate
https://syzkaller.appspot.com/bug?extid=39b75c02b8be0a061bfc
<3> 130 Yes INFO: task hung in bdev_release
https://syzkaller.appspot.com/bug?extid=4da851837827326a7cd4
<4> 49 Yes KASAN: use-after-free Read in __dev_queue_xmit (5)
https://syzkaller.appspot.com/bug?extid=b7be9429f37d15205470
<5> 35 Yes INFO: task hung in nbd_add_socket (2)
https://syzkaller.appspot.com/bug?extid=cbb4b1ebc70d0c5a8c29
<6> 15 Yes INFO: task hung in truncate_inode_pages
https://syzkaller.appspot.com/bug?extid=bae3c73c7bf2fe3a740b
<7> 7 Yes WARNING in get_probe_ref
https://syzkaller.appspot.com/bug?extid=8672dcb9d10011c0a160
<8> 4 Yes INFO: task hung in blk_trace_remove (2)
https://syzkaller.appspot.com/bug?extid=2373f6be3e6de4f92562
<9> 1 No possible deadlock in mempool_free
https://syzkaller.appspot.com/bug?extid=03a410b5470dc0d57748
---
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:[~2024-03-12 9:29 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=0000000000005570bc0613734b42@google.com \
--to=syzbot+listcaaffe0cc9b9e6b9b16d@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.