[<prev] [next>] [day] [month] [year] [list]
Message-ID: <6710bfe3.050a0220.d5849.0024.GAE@google.com>
Date: Thu, 17 Oct 2024 00:42:27 -0700
From: syzbot <syzbot+list7024578d089e5b0fc702@...kaller.appspotmail.com>
To: linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: [syzbot] Monthly ext4 report (Oct 2024)
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, 39 issues are still open and 145 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 11585 Yes WARNING: locking bug in ext4_move_extents
https://syzkaller.appspot.com/bug?extid=7f4a6f7f7051474e40ad
<2> 3767 Yes possible deadlock in dqget
https://syzkaller.appspot.com/bug?extid=6e493c165d26d6fcbf72
<3> 1711 Yes INFO: task hung in sync_inodes_sb (5)
https://syzkaller.appspot.com/bug?extid=30476ec1b6dc84471133
<4> 1444 Yes kernel BUG in ext4_do_writepages
https://syzkaller.appspot.com/bug?extid=d1da16f03614058fdc48
<5> 1354 Yes INFO: task hung in jbd2_journal_commit_transaction (5)
https://syzkaller.appspot.com/bug?extid=3071bdd0a9953bc0d177
<6> 847 Yes WARNING: locking bug in ext4_ioctl
https://syzkaller.appspot.com/bug?extid=a3c8e9ac9f9d77240afd
<7> 816 Yes WARNING: locking bug in __ext4_ioctl
https://syzkaller.appspot.com/bug?extid=a537ff48a9cb940d314c
<8> 516 No INFO: task hung in sb_start_write
https://syzkaller.appspot.com/bug?extid=fb3ada58a6c0a3208821
<9> 128 No WARNING in ext4_write_inode (2)
https://syzkaller.appspot.com/bug?extid=748cc361874fca7d33cc
<10> 102 Yes INFO: rcu detected stall in sys_clock_adjtime
https://syzkaller.appspot.com/bug?extid=25b7addb06e92c482190
---
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@...glegroups.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.
Powered by blists - more mailing lists