From: syzbot <syzbot+listf3d5bbbfec0bf4bb25ee@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 (Dec 2024)
Date: Thu, 19 Dec 2024 13:34:28 -0800 [thread overview]
Message-ID: <67649164.050a0220.1dcc64.0037.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, 10 issues are still open and 49 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1209 Yes INFO: task hung in f2fs_balance_fs
https://syzkaller.appspot.com/bug?extid=8b85865808c8908a0d8c
<2> 73 No INFO: task hung in vfs_rename
https://syzkaller.appspot.com/bug?extid=6165bc9800cd6e1fe958
<3> 56 Yes WARNING in f2fs_unlink
https://syzkaller.appspot.com/bug?extid=b01a36acd7007e273a83
<4> 16 Yes WARNING in f2fs_rename2
https://syzkaller.appspot.com/bug?extid=82064afd8bd59070fc22
<5> 6 No WARNING: locking bug in f2fs_getxattr (2)
https://syzkaller.appspot.com/bug?extid=44090b62afaabafe828a
<6> 6 Yes kernel BUG in f2fs_evict_inode (4)
https://syzkaller.appspot.com/bug?extid=5c81eb8c0a380fa578b5
<7> 6 No kernel BUG in new_curseg (2)
https://syzkaller.appspot.com/bug?extid=15669ec8c35ddf6c3d43
---
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:[~2024-12-19 21:34 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=67649164.050a0220.1dcc64.0037.GAE@google.com \
--to=syzbot+listf3d5bbbfec0bf4bb25ee@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
all inboxes | Powered by JetHome®