From: syzbot <syzbot+listc4528d3e21bc58f7fcb2@syzkaller.appspotmail.com>
To: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly ext4 report (Jul 2026)
Date: Fri, 10 Jul 2026 13:32:36 -0700 [thread overview]
Message-ID: <6a5156e4.278cdcd2.e885.0006.GAE@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 0 were fixed.
In total, 44 issues are still open and 178 have already been fixed.
There are also 8 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 16116 Yes possible deadlock in ext4_writepages (2)
https://syzkaller.appspot.com/bug?extid=eb5b4ef634a018917f3c
<2> 7757 Yes KASAN: out-of-bounds Read in ext4_xattr_set_entry
https://syzkaller.appspot.com/bug?extid=f792df426ff0f5ceb8d1
<3> 132 Yes WARNING in ext4_iomap_begin (3)
https://syzkaller.appspot.com/bug?extid=626aa13bf52efc3aa86e
<4> 30 No possible deadlock in evict (4)
https://syzkaller.appspot.com/bug?extid=a30a00d3e694e4fa1315
<5> 7 Yes divide error in qnx6_mmi_fill_super
https://syzkaller.appspot.com/bug?extid=6a0633f11d3fb88860bf
<6> 4 No WARNING in jbd2_journal_dirty_metadata (3)
https://syzkaller.appspot.com/bug?extid=a5f824f1c49dd97fcff0
<7> 3 Yes INFO: task hung in ext4_write_end
https://syzkaller.appspot.com/bug?extid=16bf7cd0ebeb1de93aa5
<8> 2998 Yes INFO: task hung in sync_inodes_sb (5)
https://syzkaller.appspot.com/bug?extid=30476ec1b6dc84471133
<9> 2204 Yes INFO: task hung in jbd2_journal_commit_transaction (5)
https://syzkaller.appspot.com/bug?extid=3071bdd0a9953bc0d177
<10> 810 Yes possible deadlock in do_writepages (2)
https://syzkaller.appspot.com/bug?extid=756f498a88797cda9299
---
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:[~2026-07-10 20:32 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=6a5156e4.278cdcd2.e885.0006.GAE@google.com \
--to=syzbot+listc4528d3e21bc58f7fcb2@syzkaller.appspotmail.com \
--cc=linux-ext4@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.