From: syzbot <syzbot+list52026f6b95687b491ce2@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 (Dec 2023)
Date: Sun, 10 Dec 2023 02:05:22 -0800 [thread overview]
Message-ID: <00000000000097ef5d060c24f422@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, 8 new issues were detected and 0 were fixed.
In total, 61 issues are still open and 115 have been fixed so far.
There are also 2 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 51616 Yes possible deadlock in console_flush_all (2)
https://syzkaller.appspot.com/bug?extid=f78380e4eae53c64125c
<2> 6748 Yes WARNING: locking bug in ext4_move_extents
https://syzkaller.appspot.com/bug?extid=7f4a6f7f7051474e40ad
<3> 546 Yes WARNING: locking bug in __ext4_ioctl
https://syzkaller.appspot.com/bug?extid=a537ff48a9cb940d314c
<4> 247 Yes WARNING: locking bug in ext4_ioctl
https://syzkaller.appspot.com/bug?extid=a3c8e9ac9f9d77240afd
<5> 152 No possible deadlock in evict (3)
https://syzkaller.appspot.com/bug?extid=dd426ae4af71f1e74729
<6> 115 Yes INFO: task hung in sync_inodes_sb (5)
https://syzkaller.appspot.com/bug?extid=30476ec1b6dc84471133
<7> 47 No KASAN: slab-use-after-free Read in check_igot_inode
https://syzkaller.appspot.com/bug?extid=741810aea4ac24243b2f
<8> 32 Yes kernel BUG in ext4_write_inline_data_end
https://syzkaller.appspot.com/bug?extid=198e7455f3a4f38b838a
<9> 16 Yes possible deadlock in ext4_xattr_inode_iget (2)
https://syzkaller.appspot.com/bug?extid=352d78bd60c8e9d6ecdc
<10> 13 Yes kernel BUG in ext4_enable_quotas
https://syzkaller.appspot.com/bug?extid=693985588d7a5e439483
---
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-12-10 10:05 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=00000000000097ef5d060c24f422@google.com \
--to=syzbot+list52026f6b95687b491ce2@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 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.