From: Chao Yu <chao@kernel.org>
To: Yongpeng Yang <monty_pavel@sina.com>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
Yongpeng Yang <yangyongpeng@xiaomi.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node()
Date: Wed, 22 Apr 2026 20:33:09 +0800 [thread overview]
Message-ID: <206a897a-2860-40b5-bbb8-829954d7e568@kernel.org> (raw)
In-Reply-To: <20260422073525.2063784-2-monty_pavel@sina.com>
On 4/22/2026 3:35 PM, Yongpeng Yang wrote:
> From: yangyongpeng <yangyongpeng@xiaomi.com>
>
> When __destroy_extent_node() sets the inode flag FI_NO_EXTENT, it does
> not reset the length of the largest extent to 0 and update the inode
> folio. Since modifications to the extent tree are disallowed afterward,
> the cached largest extent may become stale. This can trigger the
> following error in xfstests generic/388:
>
> F2FS-fs (dm-0): sanity_check_extent_cache: inode (ino=1761) extent info [220057, 57, 6] is incorrect, run fsck to fix
>
> In the f2fs_drop_inode path, __destroy_extent_node() does not need to
> guarantee that et->node_cnt is 0, because concurrency with writeback
> is expected in this path, and writeback may update the extent cache.
>
> This patch updates __destroy_extent_node() to avoid setting the inode
> flag FI_NO_EXTENT, and to remove the check zero of et->node_cnt.
>
> Fixes: ed78aeebef05 ("f2fs: fix node_cnt race between extent node destroy and writeback")
> Cc: stable@vger.kernel.org
> Reported-by: Chao Yu <chao@kernel.org>
> Suggested-by: Chao Yu <chao@kernel.org>
> Signed-off-by: yangyongpeng <yangyongpeng@xiaomi.com>
> ---
> fs/f2fs/extent_cache.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/fs/f2fs/extent_cache.c b/fs/f2fs/extent_cache.c
> index 87169fd29d89..3adbead27953 100644
> --- a/fs/f2fs/extent_cache.c
> +++ b/fs/f2fs/extent_cache.c
> @@ -645,14 +645,10 @@ static unsigned int __destroy_extent_node(struct inode *inode,
>
> while (atomic_read(&et->node_cnt)) {
> write_lock(&et->lock);
> - if (!is_inode_flag_set(inode, FI_NO_EXTENT))
> - set_inode_flag(inode, FI_NO_EXTENT);
We'd better revert all change lines in "f2fs: fix node_cnt race between
extent node destroy and writeback"?
Thanks,
> node_cnt += __free_extent_tree(sbi, et, nr_shrink);
> write_unlock(&et->lock);
> }
>
> - f2fs_bug_on(sbi, atomic_read(&et->node_cnt));
> -
> return node_cnt;
> }
>
prev parent reply other threads:[~2026-04-22 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 7:35 [PATCH] f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node() Yongpeng Yang
2026-04-22 12:33 ` Chao Yu [this message]
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=206a897a-2860-40b5-bbb8-829954d7e568@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=monty_pavel@sina.com \
--cc=stable@vger.kernel.org \
--cc=yangyongpeng@xiaomi.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