Re: [f2fs-dev] [PATCH 0/2] f2fs: fix data consistency issue caused by nat_entry flag

[patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>]

Hello:

This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Tue, 10 Mar 2026 17:36:10 +0800 you wrote:
> From: Yongpeng Yang <yangyongpeng@xiaomi.com>
> 
> This patchset addresses a data consistency issue caused by the lack of
> mutual exclusion between checks of the HAS_FSYNCED_INODE,
> IS_CHECKPOINTED, and HAS_LAST_FSYNC flags and the checkpoint write path.
> 
> In f2fs_flush_nat_entries(), after writing back the NAT block, the code
> sets HAS_LAST_FSYNC and IS_CHECKPOINTED, and clears HAS_FSYNCED_INODE.
> Although accesses and updates to these flags are protected by
> nm_i->nat_tree_lock, observing this state in the fsync context does not
> guarantee that the corresponding nat_entry state has already been
> persisted to the device.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,1/2] f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage
    (no matching commit)
  - [f2fs-dev,2/2] f2fs: fix data loss caused by incorrect use of nat_entry flag
    https://git.kernel.org/jaegeuk/f2fs/c/06d5ce7683fe

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel