From: syzbot <syzbot+lista0009dd96368e51bfdc6@syzkaller.appspotmail.com>
To: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly ext4 report (Mar 2025)
Date: Mon, 24 Mar 2025 11:56:29 -0700 [thread overview]
Message-ID: <67e1aadd.050a0220.a7ebc.002e.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, 57 issues are still open and 148 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 72595 Yes WARNING in inode_set_cached_link
https://syzkaller.appspot.com/bug?extid=2cca5ef7e5ed862c0799
<2> 41454 Yes possible deadlock in dqget
https://syzkaller.appspot.com/bug?extid=6e493c165d26d6fcbf72
<3> 4909 Yes WARNING in __ext4_iget
https://syzkaller.appspot.com/bug?extid=2ff67872645e5b5ebdd5
<4> 2297 Yes INFO: task hung in sync_inodes_sb (5)
https://syzkaller.appspot.com/bug?extid=30476ec1b6dc84471133
<5> 2060 Yes kernel BUG in ext4_do_writepages
https://syzkaller.appspot.com/bug?extid=d1da16f03614058fdc48
<6> 1944 Yes INFO: task hung in jbd2_journal_commit_transaction (5)
https://syzkaller.appspot.com/bug?extid=3071bdd0a9953bc0d177
<7> 1226 Yes KASAN: out-of-bounds Read in ext4_xattr_set_entry
https://syzkaller.appspot.com/bug?extid=f792df426ff0f5ceb8d1
<8> 243 No KCSAN: data-race in generic_buffers_fsync_noflush / writeback_single_inode (3)
https://syzkaller.appspot.com/bug?extid=35257a2200785ea628f5
<9> 183 Yes KMSAN: uninit-value in aes_encrypt (5)
https://syzkaller.appspot.com/bug?extid=aeb14e2539ffb6d21130
<10> 132 Yes INFO: task hung in do_get_write_access (3)
https://syzkaller.appspot.com/bug?extid=e7c786ece54bad9d1e43
---
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-03-24 18:56 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=67e1aadd.050a0220.a7ebc.002e.GAE@google.com \
--to=syzbot+lista0009dd96368e51bfdc6@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
all inboxes | Powered by JetHome®