[<prev] [next>] [day] [month] [year] [list]
Message-ID: <000000000000fbc4600617c8e744@google.com>
Date: Mon, 06 May 2024 06:18:33 -0700
From: syzbot <syzbot+listf1bffba7342098843795@...kaller.appspotmail.com>
To: konishi.ryusuke@...il.com, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-nilfs@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: [syzbot] Monthly nilfs report (May 2024)
Hello nilfs maintainers/developers,
This is a 31-day syzbot report for the nilfs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/nilfs
During the period, 3 new issues were detected and 1 were fixed.
In total, 7 issues are still open and 42 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 127 Yes KMSAN: uninit-value in nilfs_add_checksums_on_logs (2)
https://syzkaller.appspot.com/bug?extid=47a017c46edb25eff048
<2> 3 No INFO: task hung in nilfs_segctor_thread (2)
https://syzkaller.appspot.com/bug?extid=c8166c541d3971bf6c87
<3> 1 No possible deadlock in nilfs_dirty_inode (3)
https://syzkaller.appspot.com/bug?extid=ca73f5a22aec76875d85
---
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