From: syzbot <syzbot+list1cc30056768fee2fad99@syzkaller.appspotmail.com>
To: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [f2fs-dev] [syzbot] Monthly f2fs report (Aug 2025)
Date: Fri, 01 Aug 2025 06:49:35 -0700 [thread overview]
Message-ID: <688cc5ef.a00a0220.26d0e1.006f.GAE@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, 11 issues are still open and 61 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 4275 Yes kernel BUG in f2fs_sync_node_pages
https://syzkaller.appspot.com/bug?extid=bcdfadd9bda9988fa52a
<2> 1288 Yes INFO: task hung in f2fs_balance_fs
https://syzkaller.appspot.com/bug?extid=8b85865808c8908a0d8c
<3> 956 Yes kernel BUG in f2fs_evict_inode (4)
https://syzkaller.appspot.com/bug?extid=5c81eb8c0a380fa578b5
<4> 50 Yes INFO: task hung in f2fs_issue_checkpoint (2)
https://syzkaller.appspot.com/bug?extid=8a7eea50810efde15b0a
<5> 42 No INFO: task hung in sb_start_write (2)
https://syzkaller.appspot.com/bug?extid=b3fba2e269970207b61d
<6> 39 Yes kernel BUG in f2fs_write_end_io
https://syzkaller.appspot.com/bug?extid=803dd716c4310d16ff3a
---
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
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+list1cc30056768fee2fad99@syzkaller.appspotmail.com>
To: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly f2fs report (Aug 2025)
Date: Fri, 01 Aug 2025 06:49:35 -0700 [thread overview]
Message-ID: <688cc5ef.a00a0220.26d0e1.006f.GAE@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, 11 issues are still open and 61 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 4275 Yes kernel BUG in f2fs_sync_node_pages
https://syzkaller.appspot.com/bug?extid=bcdfadd9bda9988fa52a
<2> 1288 Yes INFO: task hung in f2fs_balance_fs
https://syzkaller.appspot.com/bug?extid=8b85865808c8908a0d8c
<3> 956 Yes kernel BUG in f2fs_evict_inode (4)
https://syzkaller.appspot.com/bug?extid=5c81eb8c0a380fa578b5
<4> 50 Yes INFO: task hung in f2fs_issue_checkpoint (2)
https://syzkaller.appspot.com/bug?extid=8a7eea50810efde15b0a
<5> 42 No INFO: task hung in sb_start_write (2)
https://syzkaller.appspot.com/bug?extid=b3fba2e269970207b61d
<6> 39 Yes kernel BUG in f2fs_write_end_io
https://syzkaller.appspot.com/bug?extid=803dd716c4310d16ff3a
---
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.
next reply other threads:[~2025-08-01 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 13:49 syzbot [this message]
2025-08-01 13:49 ` [syzbot] Monthly f2fs report (Aug 2025) 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=688cc5ef.a00a0220.26d0e1.006f.GAE@google.com \
--to=syzbot+list1cc30056768fee2fad99@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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: link
Be 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.