From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Yongpeng Yang <monty_pavel@sina.com>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Yongpeng Yang <yangyongpeng@xiaomi.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage
Date: Wed, 11 Mar 2026 16:39:22 +0800 [thread overview]
Message-ID: <3c04a285-7161-4e4c-884e-ca96bb818d3b@kernel.org> (raw)
In-Reply-To: <20260310093611.2865092-4-monty_pavel@sina.com>
On 3/10/26 17:36, Yongpeng Yang wrote:
> From: Yongpeng Yang <yangyongpeng@xiaomi.com>
>
> f2fs_need_dentry_mark() reads nat_entry flags without mutual exclusion
> with the checkpoint path, which can result in an incorrect inode block
> marking state. The scenario is as follows:
>
> create & write & fsync 'file A' write checkpoint
> - f2fs_do_sync_file // inline inode
> - f2fs_write_inode // inode folio is dirty
> - f2fs_write_checkpoint
> - f2fs_flush_merged_writes
> - f2fs_sync_node_pages
> - f2fs_fsync_node_pages // no dirty node
> - f2fs_need_inode_block_update // return true
> - f2fs_fsync_node_pages // inode dirtied
> - f2fs_need_dentry_mark //return true
> - f2fs_flush_nat_entries
> - f2fs_write_checkpoint end
> - __write_node_folio // inode with DENT_BIT_SHIFT set
> SPO, "fsck --dry-run" find inode has already checkpointed but still
> with DENT_BIT_SHIFT set
>
> The state observed by f2fs_need_dentry_mark() can differ from the state
> observed in __write_node_folio() after acquiring sbi->node_write. The
> root cause is that the semantics of IS_CHECKPOINTED and
> HAS_FSYNCED_INODE are only guaranteed after the checkpoint write has
> fully completed.
>
> This patch moves set_dentry_mark() into __write_node_folio() and
> protects it with the sbi->node_write lock.
>
Cc: stable@kernel.org
> Fixes: 88bd02c9472a ("f2fs: fix conditions to remain recovery information in f2fs_sync_file")
> Signed-off-by: Yongpeng Yang <yangyongpeng@xiaomi.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-03-11 8:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 9:36 [f2fs-dev] [PATCH 0/2] f2fs: fix data consistency issue caused by nat_entry flag Yongpeng Yang
2026-03-10 9:36 ` [f2fs-dev] [PATCH 1/2] f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage Yongpeng Yang
2026-03-11 8:39 ` Chao Yu via Linux-f2fs-devel [this message]
2026-03-11 18:16 ` Jaegeuk Kim via Linux-f2fs-devel
2026-03-12 1:13 ` Chao Yu via Linux-f2fs-devel
2026-03-12 4:01 ` Yongpeng Yang
2026-03-10 9:36 ` [f2fs-dev] [PATCH 2/2] f2fs: fix data loss caused by incorrect use of nat_entry flag Yongpeng Yang
2026-03-11 8:48 ` Chao Yu via Linux-f2fs-devel
2026-03-24 17:32 ` [f2fs-dev] [PATCH 0/2] f2fs: fix data consistency issue caused by " patchwork-bot+f2fs--- via Linux-f2fs-devel
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=3c04a285-7161-4e4c-884e-ca96bb818d3b@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=monty_pavel@sina.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.