From: syzbot <syzbot+list2032c8f48b9cdc43ce58@syzkaller.appspotmail.com>
To: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly ext4 report (Jul 2024)
Date: Mon, 15 Jul 2024 07:03:28 -0700 [thread overview]
Message-ID: <00000000000080c9c5061d49b1d4@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, 6 new issues were detected and 0 were fixed.
In total, 39 issues are still open and 134 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 893 Yes INFO: task hung in sync_inodes_sb (5)
https://syzkaller.appspot.com/bug?extid=30476ec1b6dc84471133
<2> 784 Yes WARNING: locking bug in __ext4_ioctl
https://syzkaller.appspot.com/bug?extid=a537ff48a9cb940d314c
<3> 595 Yes WARNING: locking bug in ext4_ioctl
https://syzkaller.appspot.com/bug?extid=a3c8e9ac9f9d77240afd
<4> 237 Yes INFO: task hung in jbd2_journal_commit_transaction (5)
https://syzkaller.appspot.com/bug?extid=3071bdd0a9953bc0d177
<5> 120 No WARNING in ext4_fileattr_get
https://syzkaller.appspot.com/bug?extid=d6a7a43c85606b87babd
<6> 111 Yes possible deadlock in ext4_xattr_inode_iget (3)
https://syzkaller.appspot.com/bug?extid=ee72b9a7aad1e5a77c5c
<7> 66 No INFO: task hung in ext4_stop_mmpd
https://syzkaller.appspot.com/bug?extid=0dd5b81275fa083055d7
<8> 47 Yes kernel BUG in ext4_write_inline_data_end (2)
https://syzkaller.appspot.com/bug?extid=0c89d865531d053abb2d
<9> 31 Yes INFO: rcu detected stall in sys_unlink (3)
https://syzkaller.appspot.com/bug?extid=c4f62ba28cc1290de764
<10> 30 Yes WARNING in fscrypt_fname_siphash
https://syzkaller.appspot.com/bug?extid=340581ba9dceb7e06fb3
---
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-07-15 14:03 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=00000000000080c9c5061d49b1d4@google.com \
--to=syzbot+list2032c8f48b9cdc43ce58@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®