From: Chao Yu <yuchao0@huawei.com>
To: Yunlong Song <yunlong.song@huawei.com>, <jaegeuk@kernel.org>,
<chao@kernel.org>, <yunlong.song@icloud.com>
Cc: <miaoxie@huawei.com>, <bintian.wang@huawei.com>,
<shengyong1@huawei.com>, <heyunlei@huawei.com>,
<linux-f2fs-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] f2fs-tools: fix overflow bug of start_sector when computing zone_align_start_offset
Date: Mon, 28 May 2018 15:29:21 +0800 [thread overview]
Message-ID: <a6732361-57a7-249b-ba75-3dd5e5bb18a2@huawei.com> (raw)
In-Reply-To: <1527322189-114752-1-git-send-email-yunlong.song@huawei.com>
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: Yunlong Song <yunlong.song@huawei.com>
> ---
> fsck/resize.c | 7 ++++---
> mkfs/f2fs_format.c | 4 ++--
> 2 files changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/fsck/resize.c b/fsck/resize.c
> index d285dd7..8ac7d45 100644
> --- a/fsck/resize.c
> +++ b/fsck/resize.c
> @@ -11,7 +11,8 @@
>
> static int get_new_sb(struct f2fs_super_block *sb)
> {
> - u_int32_t zone_size_bytes, zone_align_start_offset;
> + u_int32_t zone_size_bytes;
> + u_int64_t zone_align_start_offset;
> u_int32_t blocks_for_sit, blocks_for_nat, blocks_for_ssa;
> u_int32_t sit_segments, nat_segments, diff, total_meta_segments;
> u_int32_t total_valid_blks_available;
> @@ -27,10 +28,10 @@ static int get_new_sb(struct f2fs_super_block *sb)
>
> zone_size_bytes = segment_size_bytes * segs_per_zone;
> zone_align_start_offset =
> - (c.start_sector * c.sector_size +
> + ((u_int64_t) c.start_sector * c.sector_size +
> 2 * F2FS_BLKSIZE + zone_size_bytes - 1) /
> zone_size_bytes * zone_size_bytes -
> - c.start_sector * c.sector_size;
> + (u_int64_t) c.start_sector * c.sector_size;
>
> set_sb(segment_count, (c.target_sectors * c.sector_size -
> zone_align_start_offset) / segment_size_bytes /
> diff --git a/mkfs/f2fs_format.c b/mkfs/f2fs_format.c
> index 0a99a77..f045e23 100644
> --- a/mkfs/f2fs_format.c
> +++ b/mkfs/f2fs_format.c
> @@ -212,10 +212,10 @@ static int f2fs_prepare_super_block(void)
> set_sb(block_count, c.total_sectors >> log_sectors_per_block);
>
> zone_align_start_offset =
> - (c.start_sector * c.sector_size +
> + ((u_int64_t) c.start_sector * c.sector_size +
> 2 * F2FS_BLKSIZE + zone_size_bytes - 1) /
> zone_size_bytes * zone_size_bytes -
> - c.start_sector * c.sector_size;
> + (u_int64_t) c.start_sector * c.sector_size;
>
> if (c.start_sector % c.sectors_per_blk) {
> MSG(1, "\t%s: Align start sector number to the page unit\n",
>
next prev parent reply other threads:[~2018-05-28 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-26 8:09 Yunlong Song
2018-05-26 11:27 ` [f2fs-dev] " Junling Zheng
2018-05-27 13:41 ` Yunlong Song
2018-05-28 7:29 ` Chao Yu [this message]
2018-05-30 2:33 ` Jaegeuk Kim
2018-05-30 6:58 ` [PATCH rebase] " Yunlong Song
2018-05-30 14:30 ` Chao Yu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a6732361-57a7-249b-ba75-3dd5e5bb18a2@huawei.com \
--to=yuchao0@huawei.com \
--cc=bintian.wang@huawei.com \
--cc=chao@kernel.org \
--cc=heyunlei@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=shengyong1@huawei.com \
--cc=yunlong.song@huawei.com \
--cc=yunlong.song@icloud.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®