[<prev] [next>] [day] [month] [year] [list]
Message-ID: <000000000000a11763060df691a7@google.com>
Date: Tue, 02 Jan 2024 05:35:16 -0800
From: syzbot <syzbot+list18d7edf8faff313be6b2@...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 (Jan 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, 1 new issues were detected and 1 were fixed.
In total, 7 issues are still open and 37 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 444 Yes kernel BUG at fs/buffer.c:LINE!
https://syzkaller.appspot.com/bug?extid=cfed5b56649bddf80d6e
<2> 15 No KMSAN: uninit-value in nilfs_add_checksums_on_logs (2)
https://syzkaller.appspot.com/bug?extid=47a017c46edb25eff048
<3> 6 Yes kernel BUG in end_buffer_async_write
https://syzkaller.appspot.com/bug?extid=5c04210f7c7f897c1e7f
<4> 1 No possible deadlock in nilfs_dirty_inode (2)
https://syzkaller.appspot.com/bug?extid=903350d47ddb4cbb7f6f
---
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