Linux-f2fs-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 2/2] f2fs: fix data loss caused by incorrect use of nat_entry flag
Date: Wed, 11 Mar 2026 16:48:20 +0800	[thread overview]
Message-ID: <1d83a0fd-77bd-43e5-b0a6-ed6dcffdbde8@kernel.org> (raw)
In-Reply-To: <20260310093611.2865092-6-monty_pavel@sina.com>

On 3/10/26 17:36, Yongpeng Yang wrote:
> From: Yongpeng Yang <yangyongpeng@xiaomi.com>
> 
> Data loss can occur when fsync is performed on a newly created file
> (before any checkpoint has been written) concurrently with a checkpoint
> operation. 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_flush_nat_entries
>  - f2fs_fsync_node_pages // no dirty node
>  - f2fs_need_inode_block_update // return false
>  SPO and lost 'file A'
> 
> f2fs_flush_nat_entries() sets the IS_CHECKPOINTED and HAS_LAST_FSYNC
> flags for the nat_entry, but this does not mean that the checkpoint has
> actually completed successfully. However, f2fs_need_inode_block_update()
> checks these flags and incorrectly assumes that the checkpoint has
> finished.
> 
> The root cause is that the semantics of IS_CHECKPOINTED and
> HAS_LAST_FSYNC are only guaranteed after the checkpoint write fully
> completes.
> 
> This patch modifies f2fs_need_inode_block_update() to acquire the
> sbi->node_write lock before reading the nat_entry flags, ensuring that
> once IS_CHECKPOINTED and HAS_LAST_FSYNC are observed to be set, the
> checkpoint operation has already completed.
> 
> Fixes: e05df3b115e7 ("f2fs: add node operations")
> 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

  reply	other threads:[~2026-03-11  8:48 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
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 [this message]
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=1d83a0fd-77bd-43e5-b0a6-ed6dcffdbde8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox