From: Chao Yu <chao@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Cc: chao@kernel.org, Daeho Jeong <daehojeong@google.com>,
stable@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: release a removed xattr node in roll-forward recovery
Date: Wed, 14 Oct 2026 11:06:51 +0800 [thread overview]
Message-ID: <520e921e-1bfd-4c45-b134-f0677a3c656a@kernel.org> (raw)
In-Reply-To: <20261013020941.4025355-1-daeho43@gmail.com>
On 10/13/26 10:09, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> When xattrs shrink enough to fit in the inline xattr area,
> write_all_xattrs() truncates the xattr node and clears i_xattr_nid. If
> the file is then fsynced without a checkpoint, only the inode block is
> written, with i_xattr_nid of 0.
>
> Roll-forward recovery starts from the checkpointed inode, whose
> i_xattr_nid still points to the old xattr node.
> f2fs_recover_inline_xattr() copies only the inline xattr area, and
> f2fs_update_inode() writes the old i_xattr_nid back. So the inode keeps
> the stale xattr node:
>
> - The node block is never released, and fsck reports "nonzero bytes in
> xattr space after end of list".
> - If the inline xattr list ends exactly at the end of the inline area,
> its terminator is read from the stale node, and the removed xattrs
> come back after recovery.
>
> When the fsynced inode has no xattr node but the checkpointed one has,
> release the old xattr node in the same way as f2fs_recover_xattr_data().
>
> Fixes: 28cdce0459cc ("f2fs: recover inline xattr data in roll-forward process")
> Cc: stable@vger.kernel.org
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
> ---
> fs/f2fs/node.c | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
> index 55008f18afd..590fdedf9c2 100644
> --- a/fs/f2fs/node.c
> +++ b/fs/f2fs/node.c
> @@ -2831,6 +2831,29 @@ int f2fs_recover_inline_xattr(struct inode *inode, struct f2fs_cached_block *ent
> f2fs_cache_wait_writeback(ientry);
> memcpy(dst_addr, src_addr, inline_size);
> update_inode:
> + /*
> + * The xattr node of the checkpoint was removed before fsync, e.g. the
> + * xattrs became small enough to fit inline. Release it as well, or
> + * the inode keeps pointing to the stale xattrs.
> + */
> + if (!ri->i_xattr_nid && F2FS_I(inode)->i_xattr_nid) {
> + struct f2fs_sb_info *sbi = F2FS_I_SB(inode);
> + struct node_info ni;
> + int err;
> +
> + err = f2fs_get_node_info(sbi, F2FS_I(inode)->i_xattr_nid,
> + &ni, false);
> + if (err) {
> + f2fs_put_cache(ientry, true);
> + return err;
> + }
> +
> + f2fs_invalidate_blocks(sbi, ni.blk_addr, 1);
> + dec_valid_node_count(sbi, inode, false);
> + set_node_addr(sbi, &ni, NULL_ADDR, false);
> + f2fs_i_xnid_write(inode, 0);
I think we need to clear dirty on xnode as well, refer to truncate_node(), otherwise
f2fs_writeback will write a dirty xnode w/ blkaddr = NULL_ADDR.
Thanks,
> + }
> +
> f2fs_update_inode(inode, ientry);
> f2fs_put_cache(ientry, true);
> return 0;
prev parent reply other threads:[~2026-10-14 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 2:09 Daeho Jeong
2026-10-14 3:06 ` 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=520e921e-1bfd-4c45-b134-f0677a3c656a@kernel.org \
--to=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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®