* [syzbot] Monthly nilfs report (Jan 2026)
@ 2026-01-12 22:00 syzbot
0 siblings, 0 replies; only message in thread
From: syzbot @ 2026-01-12 22:00 UTC (permalink / raw)
To: konishi.ryusuke, linux-kernel, linux-nilfs, syzkaller-bugs
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, 0 new issues were detected and 0 were fixed.
In total, 6 issues are still open and 64 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 10 Yes WARNING in nilfs_rename (2)
https://syzkaller.appspot.com/bug?extid=f6c7e1f1809f235eeb90
<2> 9 Yes WARNING in nilfs_btree_assign (3)
https://syzkaller.appspot.com/bug?extid=158be45e4d99232e1900
<3> 4 Yes INFO: task hung in nilfs_segctor_thread (6)
https://syzkaller.appspot.com/bug?extid=7eedce5eb281acd832f0
---
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-01-12 22:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-01-12 22:00 [syzbot] Monthly nilfs report (Jan 2026) syzbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox