From: syzbot <syzbot+list79b0622b9b462d592968@syzkaller.appspotmail.com>
To: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly ext4 report (Jun 2026)
Date: Tue, 09 Jun 2026 13:32:32 -0700 [thread overview]
Message-ID: <6a287860.39669fcc.33b062.009d.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, 2 new issues were detected and 0 were fixed.
In total, 45 issues are still open and 175 have already been fixed.
There are also 8 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 10098 Yes possible deadlock in ext4_writepages (2)
https://syzkaller.appspot.com/bug?extid=eb5b4ef634a018917f3c
<2> 7580 Yes KASAN: out-of-bounds Read in ext4_xattr_set_entry
https://syzkaller.appspot.com/bug?extid=f792df426ff0f5ceb8d1
<3> 3212 Yes kernel BUG in ext4_do_writepages
https://syzkaller.appspot.com/bug?extid=d1da16f03614058fdc48
<4> 481 Yes possible deadlock in ext4_evict_inode (5)
https://syzkaller.appspot.com/bug?extid=212e8f62790f8e0bc63b
<5> 406 Yes possible deadlock in wait_transaction_locked (3)
https://syzkaller.appspot.com/bug?extid=5d19358d7eb30ffb0cc5
<6> 139 Yes KMSAN: uninit-value in fscrypt_crypt_data_unit
https://syzkaller.appspot.com/bug?extid=7add5c56bc2a14145d20
<7> 20 No possible deadlock in evict (4)
https://syzkaller.appspot.com/bug?extid=a30a00d3e694e4fa1315
<8> 10 No WARNING in ext4_write_inode (3)
https://syzkaller.appspot.com/bug?extid=070d9738dbe6a10fadc8
<9> 8 Yes INFO: task hung in block_read_full_folio (3)
https://syzkaller.appspot.com/bug?extid=03afbb29537f0336b7ad
<10> 2951 Yes INFO: task hung in sync_inodes_sb (5)
https://syzkaller.appspot.com/bug?extid=30476ec1b6dc84471133
---
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-06-09 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=6a287860.39669fcc.33b062.009d.GAE@google.com \
--to=syzbot+list79b0622b9b462d592968@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox