From: kth5965@gmail.com
To: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: evict: truncate page cache before clear_inode
Date: Fri, 20 Mar 2026 00:11:21 +0900 [thread overview]
Message-ID: <20260319151121.39737-1-kth5965@gmail.com> (raw)
In-Reply-To: <b044d785-cf71-4186-b208-c375c605893b@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.
next prev parent reply other threads:[~2026-03-19 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 16:06 [PATCH] f2fs: evict: truncate page cache before clear_inode Taerang Kim
2026-02-24 16:54 ` [PATCH v2] " Taerang Kim
2026-03-09 7:44 ` Chao Yu
2026-03-09 14:25 ` [f2fs-dev] " kth5965
2026-03-13 7:45 ` Chao Yu
2026-03-17 15:28 ` kth5965
2026-03-18 3:40 ` Chao Yu
2026-03-19 15:11 ` kth5965 [this message]
2026-03-23 3:14 ` Chao Yu
2026-03-31 15:24 ` kth5965
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=20260319151121.39737-1-kth5965@gmail.com \
--to=kth5965@gmail.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