kth...@gmail.com
unread,Mar 19, 2026, 12:57:43 PM (4 days ago) Mar 19Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to ch...@kernel.org, jae...@kernel.org, linux-f2...@lists.sourceforge.net, syzkall...@googlegroups.com, linux-...@vger.kernel.org
Hi Chao,
Yes, I agree with your point.
I also think 2) is useful to detect the corrupted inode earlier and to
make the issue visible through log and returned error.
But 2) alone does not seem sufficient, because we can still reach inode
cleanup later, and then `f2fs_evict_inode()` can still go through the
inline conversion path.
So it makes sense to me that we need both:
1. earlier detection / guarding in sanity check
2. fixing the empty inline conversion path so page #0 cache is not left
behind
If this understanding is correct, I will prepare the fix in that
direction.
Thanks.