From: syzbot <syzbot+list9a35871b40c53fa1b44b@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: [syzbot] Monthly ext4 report (Mar 2024)
Date: Tue, 12 Mar 2024 02:29:28 -0700 [thread overview]
Message-ID: <0000000000007bfda60613734bdf@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, 1 new issues were detected and 0 were fixed.
In total, 24 issues are still open and 130 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 8629 Yes WARNING: locking bug in ext4_move_extents
https://syzkaller.appspot.com/bug?extid=7f4a6f7f7051474e40ad
<2> 697 Yes WARNING: locking bug in __ext4_ioctl
https://syzkaller.appspot.com/bug?extid=a537ff48a9cb940d314c
<3> 401 Yes WARNING: locking bug in ext4_ioctl
https://syzkaller.appspot.com/bug?extid=a3c8e9ac9f9d77240afd
<4> 173 No possible deadlock in evict (3)
https://syzkaller.appspot.com/bug?extid=dd426ae4af71f1e74729
<5> 81 No WARNING in ext4_write_inode (2)
https://syzkaller.appspot.com/bug?extid=748cc361874fca7d33cc
<6> 23 No possible deadlock in ext4_da_get_block_prep
https://syzkaller.appspot.com/bug?extid=a86b193140e10df1aff2
<7> 22 No possible deadlock in start_this_handle (4)
https://syzkaller.appspot.com/bug?extid=cf0b4280f19be4031cf2
<8> 18 Yes INFO: rcu detected stall in sys_unlink (3)
https://syzkaller.appspot.com/bug?extid=c4f62ba28cc1290de764
<9> 18 Yes kernel BUG in __ext4_journal_stop
https://syzkaller.appspot.com/bug?extid=bdab24d5bf96d57c50b0
<10> 7 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-03-12 9:29 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=0000000000007bfda60613734bdf@google.com \
--to=syzbot+list9a35871b40c53fa1b44b@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).