From: syzbot <syzbot+listf5045cc3857cd5f3f4c2@syzkaller.appspotmail.com> To: chao@kernel.org, jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Subject: [syzbot] Monthly f2fs report (Jun 2023) Date: Tue, 06 Jun 2023 16:21:54 -0700 [thread overview] Message-ID: <000000000000ef407105fd7e485e@google.com> (raw) Hello f2fs maintainers/developers, This is a 31-day syzbot report for the f2fs subsystem. All related reports/information can be found at: https://syzkaller.appspot.com/upstream/s/f2fs During the period, 0 new issues were detected and 0 were fixed. In total, 16 issues are still open and 28 have been fixed so far. Some of the still happening issues: Ref Crashes Repro Title <1> 187 Yes INFO: task hung in f2fs_balance_fs https://syzkaller.appspot.com/bug?extid=8b85865808c8908a0d8c <2> 63 Yes kernel BUG in f2fs_evict_inode https://syzkaller.appspot.com/bug?extid=e1246909d526a9d470fa <3> 4 Yes WARNING: lock held when returning to user space in f2fs_write_single_data_page https://syzkaller.appspot.com/bug?extid=eb6201248f684e99b9f8 --- 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+listf5045cc3857cd5f3f4c2@syzkaller.appspotmail.com> To: chao@kernel.org, jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Subject: [f2fs-dev] [syzbot] Monthly f2fs report (Jun 2023) Date: Tue, 06 Jun 2023 16:21:54 -0700 [thread overview] Message-ID: <000000000000ef407105fd7e485e@google.com> (raw) Hello f2fs maintainers/developers, This is a 31-day syzbot report for the f2fs subsystem. All related reports/information can be found at: https://syzkaller.appspot.com/upstream/s/f2fs During the period, 0 new issues were detected and 0 were fixed. In total, 16 issues are still open and 28 have been fixed so far. Some of the still happening issues: Ref Crashes Repro Title <1> 187 Yes INFO: task hung in f2fs_balance_fs https://syzkaller.appspot.com/bug?extid=8b85865808c8908a0d8c <2> 63 Yes kernel BUG in f2fs_evict_inode https://syzkaller.appspot.com/bug?extid=e1246909d526a9d470fa <3> 4 Yes WARNING: lock held when returning to user space in f2fs_write_single_data_page https://syzkaller.appspot.com/bug?extid=eb6201248f684e99b9f8 --- 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. _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2023-06-06 23:22 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-06 23:21 syzbot [this message] 2023-06-06 23:21 ` [f2fs-dev] [syzbot] Monthly f2fs report (Jun 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=000000000000ef407105fd7e485e@google.com \ --to=syzbot+listf5045cc3857cd5f3f4c2@syzkaller.appspotmail.com \ --cc=chao@kernel.org \ --cc=jaegeuk@kernel.org \ --cc=linux-f2fs-devel@lists.sourceforge.net \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@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.