From: syzbot <syzbot+list89334176c7333521aa2c@syzkaller.appspotmail.com>
To: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly ext4 report (Jun 2024)
Date: Fri, 14 Jun 2024 01:14:20 -0700 [thread overview]
Message-ID: <000000000000d4e4a1061ad53398@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, 8 new issues were detected and 0 were fixed.
In total, 38 issues are still open and 134 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 9744 Yes WARNING: locking bug in ext4_move_extents
https://syzkaller.appspot.com/bug?extid=7f4a6f7f7051474e40ad
<2> 767 Yes WARNING: locking bug in __ext4_ioctl
https://syzkaller.appspot.com/bug?extid=a537ff48a9cb940d314c
<3> 547 Yes WARNING: locking bug in ext4_ioctl
https://syzkaller.appspot.com/bug?extid=a3c8e9ac9f9d77240afd
<4> 491 Yes INFO: task hung in sync_inodes_sb (5)
https://syzkaller.appspot.com/bug?extid=30476ec1b6dc84471133
<5> 452 No possible deadlock in evict (3)
https://syzkaller.appspot.com/bug?extid=dd426ae4af71f1e74729
<6> 265 Yes KMSAN: uninit-value in ext4_inlinedir_to_tree
https://syzkaller.appspot.com/bug?extid=eaba5abe296837a640c0
<7> 248 Yes WARNING in __fortify_report
https://syzkaller.appspot.com/bug?extid=50835f73143cc2905b9e
<8> 226 No possible deadlock in __ext4_mark_inode_dirty (3)
https://syzkaller.appspot.com/bug?extid=72c7e5a0d9f5901e864e
<9> 155 Yes INFO: task hung in jbd2_journal_commit_transaction (5)
https://syzkaller.appspot.com/bug?extid=3071bdd0a9953bc0d177
<10> 32 Yes kernel BUG in ext4_write_inline_data_end (2)
https://syzkaller.appspot.com/bug?extid=0c89d865531d053abb2d
---
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:[~2024-06-14 8:14 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=000000000000d4e4a1061ad53398@google.com \
--to=syzbot+list89334176c7333521aa2c@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.