From: syzbot <syzbot+list6dfc6ea307bfacecbbe0@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: [syzbot] Monthly ext4 report (Apr 2023)
Date: Fri, 28 Apr 2023 08:06:51 -0700 [thread overview]
Message-ID: <000000000000a89a6a05fa66d226@google.com> (raw)
Hello ext4 maintainers/developers,
This is a 31-day syzbot report for the ext4 subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/ext4
During the period, 6 new issues were detected and 0 were fixed.
In total, 72 issues are still open and 82 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 83130 Yes possible deadlock in jbd2_journal_lock_updates
https://syzkaller.appspot.com/bug?extid=79e6bbabf3ce17357969
<2> 7208 Yes WARNING in ext4_dirty_folio
https://syzkaller.appspot.com/bug?extid=ecab51a4a5b9f26eeaa1
<3> 5604 Yes possible deadlock in dquot_commit (2)
https://syzkaller.appspot.com/bug?extid=70ff52e51b7e7714db8a
<4> 773 Yes INFO: task hung in __sync_dirty_buffer
https://syzkaller.appspot.com/bug?extid=91dccab7c64e2850a4e5
<5> 476 No possible deadlock in ext4_map_blocks
https://syzkaller.appspot.com/bug?extid=6de5025c31d33047d2a4
<6> 361 No possible deadlock in ext4_multi_mount_protect
https://syzkaller.appspot.com/bug?extid=6b7df7d5506b32467149
<7> 203 Yes kernel BUG in ext4_get_group_info
https://syzkaller.appspot.com/bug?extid=e2efa3efc15a1c9e95c3
<8> 93 Yes kernel BUG in ext4_do_writepages
https://syzkaller.appspot.com/bug?extid=d1da16f03614058fdc48
<9> 29 Yes KASAN: slab-out-of-bounds Read in ext4_enable_quotas
https://syzkaller.appspot.com/bug?extid=ea70429cd5cf47ba8937
<10> 22 Yes WARNING in ext4_xattr_block_set (2)
https://syzkaller.appspot.com/bug?extid=6385d7d3065524c5ca6d
---
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:[~2023-04-28 15:07 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=000000000000a89a6a05fa66d226@google.com \
--to=syzbot+list6dfc6ea307bfacecbbe0@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).