From: syzbot <syzbot+fc026e87558558f75c00@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: [syzbot] [f2fs?] kernel BUG in clear_inode (5)
Date: Tue, 24 Feb 2026 06:44:37 -0800 [thread overview]
Message-ID: <699db955.a00a0220.31e421.02eb.GAE@google.com> (raw)
In-Reply-To: <6982985a.a00a0220.37c87e.0017.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] [f2fs?] kernel BUG in clear_inode (5)
Author: kth5965@gmail.com
#syz test: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
diff --git a/fs/f2fs/inode.c b/fs/f2fs/inode.c
index 38b8994bc1b2..914a0966a1c5 100644
--- a/fs/f2fs/inode.c
+++ b/fs/f2fs/inode.c
@@ -1001,6 +1001,13 @@ void f2fs_evict_inode(struct inode *inode)
out_clear:
fscrypt_put_encryption_info(inode);
fsverity_cleanup_inode(inode);
+ /*
+ * Pages in inode's data mapping may have been re-added during
+ * eviction, e.g. by f2fs_convert_inline_inode() called from
+ * f2fs_truncate(). Truncate them again before clear_inode()
+ * which expects nrpages == 0.
+ */
+ truncate_inode_pages_final(&inode->i_data);
clear_inode(inode);
}
next prev parent reply other threads:[~2026-02-24 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 0:52 [syzbot] [f2fs?] kernel BUG in clear_inode (5) syzbot
2026-02-05 11:55 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git f14faaf3a1fb3b9e4cf2e56269711fb85fba9458 syzbot
2026-02-24 14:44 ` syzbot [this message]
2026-02-24 14:52 ` Forwarded: Re: [syzbot] [f2fs?] kernel BUG in clear_inode (5) 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=699db955.a00a0220.31e421.02eb.GAE@google.com \
--to=syzbot+fc026e87558558f75c00@syzkaller.appspotmail.com \
--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