From: syzbot <syzbot+liste73a7dcf846b305a7eb2@syzkaller.appspotmail.com>
To: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly ext4 report (Apr 2024)
Date: Fri, 12 Apr 2024 06:18:21 -0700 [thread overview]
Message-ID: <000000000000158d280615e61beb@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 1 were fixed.
In total, 27 issues are still open and 131 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 8793 Yes WARNING: locking bug in ext4_move_extents
https://syzkaller.appspot.com/bug?extid=7f4a6f7f7051474e40ad
<2> 706 Yes WARNING: locking bug in __ext4_ioctl
https://syzkaller.appspot.com/bug?extid=a537ff48a9cb940d314c
<3> 435 Yes WARNING: locking bug in ext4_ioctl
https://syzkaller.appspot.com/bug?extid=a3c8e9ac9f9d77240afd
<4> 151 Yes INFO: task hung in sync_inodes_sb (5)
https://syzkaller.appspot.com/bug?extid=30476ec1b6dc84471133
<5> 33 Yes KASAN: wild-memory-access Read in read_block_bitmap
https://syzkaller.appspot.com/bug?extid=47f3372b693d7f62b8ae
<6> 20 Yes INFO: task hung in ext4_quota_write
https://syzkaller.appspot.com/bug?extid=a43d4f48b8397d0e41a9
<7> 19 Yes INFO: rcu detected stall in sys_unlink (3)
https://syzkaller.appspot.com/bug?extid=c4f62ba28cc1290de764
<8> 13 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-04-12 13:18 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=000000000000158d280615e61beb@google.com \
--to=syzbot+liste73a7dcf846b305a7eb2@syzkaller.appspotmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).