From: syzbot <syzbot+list5ea887c46d22b2acf805@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 (May 2023)
Date: Tue, 30 May 2023 05:38:55 -0700 [thread overview]
Message-ID: <000000000000834af205fce87c00@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, 3 new issues were detected and 10 were fixed.
In total, 46 issues are still open and 106 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 124 Yes kernel BUG in ext4_do_writepages
https://syzkaller.appspot.com/bug?extid=d1da16f03614058fdc48
<2> 48 No WARNING in ext4_write_inode (2)
https://syzkaller.appspot.com/bug?extid=748cc361874fca7d33cc
<3> 8 Yes WARNING in ext4_da_update_reserve_space (2)
https://syzkaller.appspot.com/bug?extid=a1232eabd7a3d43d4fb5
<4> 8 Yes kernel BUG in __ext4_journal_stop
https://syzkaller.appspot.com/bug?extid=bdab24d5bf96d57c50b0
<5> 7 Yes kernel BUG in ext4_write_inline_data
https://syzkaller.appspot.com/bug?extid=f4582777a19ec422b517
---
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.
next reply other threads:[~2023-05-30 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 12:38 syzbot [this message]
2023-06-01 2:08 ` [syzbot] Monthly ext4 report (May 2023) Baokun Li
2023-06-02 21:06 ` Theodore Ts'o
2023-06-03 2:05 ` Baokun Li
2023-06-03 4:30 ` Theodore Ts'o
2023-06-03 6:20 ` Baokun Li
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=000000000000834af205fce87c00@google.com \
--to=syzbot+list5ea887c46d22b2acf805@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.