From: syzbot <syzbot+listc16d6233751953300e09@syzkaller.appspotmail.com>
To: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly ext4 report (Oct 2025)
Date: Wed, 29 Oct 2025 02:02:29 -0700 [thread overview]
Message-ID: <6901d825.050a0220.32483.0205.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 1 were fixed.
In total, 50 issues are still open and 163 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3903 Yes KASAN: out-of-bounds Read in ext4_xattr_set_entry
https://syzkaller.appspot.com/bug?extid=f792df426ff0f5ceb8d1
<2> 2813 Yes kernel BUG in ext4_do_writepages
https://syzkaller.appspot.com/bug?extid=d1da16f03614058fdc48
<3> 2779 Yes INFO: task hung in sync_inodes_sb (5)
https://syzkaller.appspot.com/bug?extid=30476ec1b6dc84471133
<4> 989 Yes WARNING in ext4_xattr_inode_lookup_create
https://syzkaller.appspot.com/bug?extid=fe42a669c87e4a980051
<5> 572 No KCSAN: data-race in generic_buffers_fsync_noflush / writeback_single_inode (3)
https://syzkaller.appspot.com/bug?extid=35257a2200785ea628f5
<6> 493 Yes possible deadlock in ext4_writepages (2)
https://syzkaller.appspot.com/bug?extid=eb5b4ef634a018917f3c
<7> 269 Yes INFO: task hung in do_renameat2 (2)
https://syzkaller.appspot.com/bug?extid=39a12f7473ed8066d2ca
<8> 266 Yes possible deadlock in ext4_xattr_inode_lookup_create
https://syzkaller.appspot.com/bug?extid=d91a6e2efb07bd3354e9
<9> 168 Yes kernel BUG in ext4_mb_use_inode_pa (2)
https://syzkaller.appspot.com/bug?extid=d79019213609e7056a19
<10> 140 Yes KASAN: use-after-free Read in ext4_find_extent (4)
https://syzkaller.appspot.com/bug?extid=ee60e584b5c6bb229126
---
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:[~2025-10-29 9:02 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=6901d825.050a0220.32483.0205.GAE@google.com \
--to=syzbot+listc16d6233751953300e09@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