From: syzbot <syzbot+list88e3b0f0499ea99b802f@syzkaller.appspotmail.com> To: konishi.ryusuke@gmail.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nilfs@vger.kernel.org, syzkaller-bugs@googlegroups.com Subject: [syzbot] Monthly nilfs report (Sep 2023) Date: Mon, 02 Oct 2023 02:42:41 -0700 [thread overview] Message-ID: <0000000000007419730606b898ed@google.com> (raw) 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, 7 issues are still open and 36 have been fixed so far. Some of the still happening issues: Ref Crashes Repro Title <1> 335 Yes WARNING in nilfs_sufile_set_segment_usage https://syzkaller.appspot.com/bug?extid=14e9f834f6ddecece094 <2> 325 Yes kernel BUG at fs/buffer.c:LINE! https://syzkaller.appspot.com/bug?extid=cfed5b56649bddf80d6e <3> 220 No INFO: task hung in path_openat (7) https://syzkaller.appspot.com/bug?extid=950a0cdaa2fdd14f5bdc <4> 95 Yes INFO: task hung in nilfs_detach_log_writer https://syzkaller.appspot.com/bug?extid=e3973c409251e136fdd0 <5> 6 Yes kernel BUG in end_buffer_async_write https://syzkaller.appspot.com/bug?extid=5c04210f7c7f897c1e7f --- 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.
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+list88e3b0f0499ea99b802f-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org> To: konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Subject: [syzbot] Monthly nilfs report (Sep 2023) Date: Mon, 02 Oct 2023 02:42:41 -0700 [thread overview] Message-ID: <0000000000007419730606b898ed@google.com> (raw) 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, 7 issues are still open and 36 have been fixed so far. Some of the still happening issues: Ref Crashes Repro Title <1> 335 Yes WARNING in nilfs_sufile_set_segment_usage https://syzkaller.appspot.com/bug?extid=14e9f834f6ddecece094 <2> 325 Yes kernel BUG at fs/buffer.c:LINE! https://syzkaller.appspot.com/bug?extid=cfed5b56649bddf80d6e <3> 220 No INFO: task hung in path_openat (7) https://syzkaller.appspot.com/bug?extid=950a0cdaa2fdd14f5bdc <4> 95 Yes INFO: task hung in nilfs_detach_log_writer https://syzkaller.appspot.com/bug?extid=e3973c409251e136fdd0 <5> 6 Yes kernel BUG in end_buffer_async_write https://syzkaller.appspot.com/bug?extid=5c04210f7c7f897c1e7f --- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org 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.
next reply other threads:[~2023-10-02 9:42 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-02 9:42 syzbot [this message] 2023-10-02 9:42 ` [syzbot] Monthly nilfs report (Sep 2023) syzbot
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=0000000000007419730606b898ed@google.com \ --to=syzbot+list88e3b0f0499ea99b802f@syzkaller.appspotmail.com \ --cc=konishi.ryusuke@gmail.com \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nilfs@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.