From: syzbot <syzbot+list6d5e07b82ce5d672a81d@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 (Nov 2025)
Date: Mon, 03 Nov 2025 05:10:34 -0800 [thread overview]
Message-ID: <6908a9ca.050a0220.29fc44.0045.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, 4 new issues were detected and 0 were fixed.
In total, 11 issues are still open and 68 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1330 Yes INFO: task hung in f2fs_balance_fs
https://syzkaller.appspot.com/bug?extid=8b85865808c8908a0d8c
<2> 1315 Yes kernel BUG in f2fs_evict_inode (4)
https://syzkaller.appspot.com/bug?extid=5c81eb8c0a380fa578b5
<3> 914 Yes WARNING in get_data
https://syzkaller.appspot.com/bug?extid=f5d91b1897d5b094c6b4
<4> 155 Yes INFO: task hung in f2fs_issue_checkpoint (2)
https://syzkaller.appspot.com/bug?extid=8a7eea50810efde15b0a
<5> 133 Yes kernel BUG in f2fs_write_end_io
https://syzkaller.appspot.com/bug?extid=803dd716c4310d16ff3a
<6> 10 No kernel BUG in __update_extent_tree_range
https://syzkaller.appspot.com/bug?extid=24124df3170c3638b35f
<7> 5 No possible deadlock in f2fs_do_truncate_blocks
https://syzkaller.appspot.com/bug?extid=14b90e1156b9f6fc1266
<8> 3 No kernel BUG in f2fs_do_truncate_blocks
https://syzkaller.appspot.com/bug?extid=1867a378155795cb1680
---
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.
reply other threads:[~2025-11-03 13:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6908a9ca.050a0220.29fc44.0045.GAE@google.com \
--to=syzbot+list6d5e07b82ce5d672a81d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome