From: syzbot <syzbot+list863fc044988daa3042ea@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 (Jul 2023)
Date: Thu, 06 Jul 2023 07:18:48 -0700 [thread overview]
Message-ID: <000000000000db94d405ffd231f7@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 3 were fixed.
In total, 51 issues are still open and 112 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1186 Yes WARNING: locking bug in ext4_move_extents
https://syzkaller.appspot.com/bug?extid=7f4a6f7f7051474e40ad
<2> 207 No INFO: task hung in path_openat (7)
https://syzkaller.appspot.com/bug?extid=950a0cdaa2fdd14f5bdc
<3> 147 Yes WARNING in ext4_file_write_iter
https://syzkaller.appspot.com/bug?extid=5050ad0fb47527b1808a
<4> 141 Yes possible deadlock in quotactl_fd
https://syzkaller.appspot.com/bug?extid=cdcd444e4d3a256ada13
<5> 115 No possible deadlock in evict (3)
https://syzkaller.appspot.com/bug?extid=dd426ae4af71f1e74729
<6> 97 Yes WARNING: locking bug in __ext4_ioctl
https://syzkaller.appspot.com/bug?extid=a537ff48a9cb940d314c
<7> 52 Yes WARNING: locking bug in ext4_ioctl
https://syzkaller.appspot.com/bug?extid=a3c8e9ac9f9d77240afd
<8> 24 Yes kernel BUG in ext4_write_inline_data_end
https://syzkaller.appspot.com/bug?extid=198e7455f3a4f38b838a
<9> 5 Yes INFO: task hung in ext4_evict_ea_inode
https://syzkaller.appspot.com/bug?extid=38e6635a03c83c76297a
<10> 5 Yes KASAN: use-after-free Read in ext4_search_dir
https://syzkaller.appspot.com/bug?extid=34a0f26f0f61c4888ea4
---
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-07-06 14:18 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=000000000000db94d405ffd231f7@google.com \
--to=syzbot+list863fc044988daa3042ea@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.