From: syzbot <syzbot+list462fc37593d30c75df84@syzkaller.appspotmail.com>
To: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly block report (Nov 2024)
Date: Mon, 18 Nov 2024 02:38:24 -0800 [thread overview]
Message-ID: <673b1920.050a0220.87769.002c.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, 8 new issues were detected and 0 were fixed.
In total, 33 issues are still open and 94 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 4450 Yes KMSAN: kernel-infoleak in filemap_read
https://syzkaller.appspot.com/bug?extid=905d785c4923bea2c1db
<2> 2406 Yes INFO: task hung in bdev_release
https://syzkaller.appspot.com/bug?extid=4da851837827326a7cd4
<3> 1643 Yes INFO: task hung in blkdev_fallocate
https://syzkaller.appspot.com/bug?extid=39b75c02b8be0a061bfc
<4> 587 No INFO: task hung in bdev_open
https://syzkaller.appspot.com/bug?extid=5c6179f2c4f1e111df11
<5> 335 Yes KASAN: slab-use-after-free Read in percpu_ref_put (2)
https://syzkaller.appspot.com/bug?extid=905d719acdbd213bf67e
<6> 287 Yes possible deadlock in blk_trace_setup
https://syzkaller.appspot.com/bug?extid=0d8542c90a512dc95185
<7> 40 No INFO: task hung in set_blocksize
https://syzkaller.appspot.com/bug?extid=3c0a6dfa116ca1e1ad1c
<8> 37 Yes INFO: task hung in nbd_add_socket (2)
https://syzkaller.appspot.com/bug?extid=cbb4b1ebc70d0c5a8c29
<9> 35 Yes INFO: task hung in blk_trace_ioctl (4)
https://syzkaller.appspot.com/bug?extid=ed812ed461471ab17a0c
<10> 28 Yes WARNING in blk_register_tracepoints
https://syzkaller.appspot.com/bug?extid=c54ded83396afee31eb1
---
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-11-18 10:38 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=673b1920.050a0220.87769.002c.GAE@google.com \
--to=syzbot+list462fc37593d30c75df84@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.