From: Yongpeng Yang <[email protected]> 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.
Signed-off-by: Yongpeng Yang <[email protected]> --- fs/f2fs/data.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c index 84746a06cd58..42f15fd9c68e 100644 --- a/fs/f2fs/data.c +++ b/fs/f2fs/data.c @@ -2102,7 +2102,7 @@ int f2fs_fiemap(struct inode *inode, struct fiemap_extent_info *fieinfo, size += F2FS_BLKSIZE; } } else if (map.m_flags & F2FS_MAP_DELALLOC) { - flags = FIEMAP_EXTENT_UNWRITTEN; + flags = FIEMAP_EXTENT_DELALLOC; } start_blk += F2FS_BYTES_TO_BLK(size); -- 2.43.0 _______________________________________________ Linux-f2fs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
