On 2018/5/26 16:09, Yunlong Song wrote:
> zone_align_start_offset should be u64, but config.start_sector is u32,
> so it may be overflow when computing zone_align_start_offset.
Could you rebase this patch on top of "f2fs-tools: fix to match with the
start_sector"?
Thanks,
>
> Signed-off-by: Yun
Just keep it same with u_int64_t defined in mkfs/f2fs_format.c, and
c.start_sector * c.sector_size
may be u32 overflow, so add (u_int64_t) before c.start_sector *
c.sector_size and change the target
value zone_align_start_offset to (u_int64_t).
On 2018/5/26 19:27, Junling Zheng wrote:
No neet
No neet to change zone_align_start_offset to u64, because
zone_align_start_offset is always
smaller than zone_size_bytes, which is u32.
Thanks,
Junling
On 2018/5/26 16:09, Yunlong Song wrote:
> zone_align_start_offset should be u64, but config.start_sector is u32,
> so it may be overflow when co
zone_align_start_offset should be u64, but config.start_sector is u32,
so it may be overflow when computing zone_align_start_offset.
Signed-off-by: Yunlong Song
---
fsck/resize.c | 7 ---
mkfs/f2fs_format.c | 4 ++--
2 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/fsck/re
4 matches
Mail list logo