A length that exceeds the real size of the inode may be
specified from user, although these out-of-range areas
are not mapped, but they still need to be check in
while loop, which is unnecessary.
Signed-off-by: Zhiguo Niu
---
v2: check i_size within inode lock according to Chao's suggestions
---
On 2024/3/25 10:14, Shinichiro Kawasaki wrote:
On Mar 24, 2024 / 20:13, Chao Yu wrote:
...
Hi Shinichiro,
Can you please check below diff? IIUC, for the case: f2fs_map_blocks()
returns zero blkaddr in non-primary device, which is a verified valid
block address, we'd better to check m_flags & F2
On Mar 24, 2024 / 20:13, Chao Yu wrote:
...
> Hi Shinichiro,
>
> Can you please check below diff? IIUC, for the case: f2fs_map_blocks()
> returns zero blkaddr in non-primary device, which is a verified valid
> block address, we'd better to check m_flags & F2FS_MAP_MAPPED instead
> of map.m_pblk !=
On 2024/3/19 19:13, Shinichiro Kawasaki wrote:
On Mar 19, 2024 / 10:22, Chao Yu wrote:
On 2024/3/18 13:47, Shinichiro Kawasaki via Linux-f2fs-devel wrote:
I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a
look in the commit, but it looks fine to me. So I thought the c
