Re: [f2fs-dev] [PATCH 1/4] f2fs: fix incorrect extent flag when physical addr is NEW_ADDR in f2fs_fiemap

[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,  3 Feb 2026 21:36:33 +0800 you wrote:
> From: Yongpeng Yang <yangyongpeng@xiaomi.com>
> 
> When the file block's address is mapped to NEW_ADDR, the extent is
> currently marked with the FIEMAP_EXTENT_UNWRITTEN flag in f2fs_fiemap().
> This flag indicates that the block has been allocated but not yet
> written to. However, NEW_ADDR indicates delayed writing, meaning the
> block has not been allocated yet. Therefore, this should be modified
> such that when a file block's address is mapped to NEW_ADDR, the extent
> is marked with the FIEMAP_EXTENT_DELALLOC flags instead.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,1/4] f2fs: fix incorrect extent flag when physical addr is NEW_ADDR in f2fs_fiemap
    (no matching commit)
  - [f2fs-dev,2/4] f2fs: fix incorrect file address mapping when inline inode is unwritten
    https://git.kernel.org/jaegeuk/f2fs/c/56528dc7fcc6
  - [f2fs-dev,3/4] f2fs: fix fiemap boundary handling when read extent cache is incomplete
    (no matching commit)
  - [f2fs-dev,4/4] f2fs: fix inline data not being written to disk in writeback path
    (no matching commit)

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