linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: zangyangyang1 <zangyangyang1@xiaomi.com>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs_io: Fix integer multiplication overflow error in fiemap
Date: Wed, 24 May 2023 11:02:48 +0800	[thread overview]
Message-ID: <4cbd654a-cbed-2acc-8fe5-898e534eb6fe@kernel.org> (raw)
In-Reply-To: <20230523122720.1628122-1-zangyangyang1@xiaomi.com>

On 2023/5/23 20:27, zangyangyang1 wrote:
> When using fiemap to obtain the block address of files
> larger than 2GB ((2147483647+1) bytes), an integer
> multiplication overflow error will occur.
> This issue is caused by the following code:
>      start = atoi(argv[1]) * F2FS_BLKSIZE;
>      length = atoi(argv[2]) * F2FS_BLKSIZE;
> 
> Signed-off-by: zangyangyang1 <zangyangyang1@xiaomi.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2023-05-24  3:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23  7:24 [f2fs-dev] [PATCH] f2fs_io: Fix integer multiplication overflow error in fiemap zangyangyang1 via Linux-f2fs-devel
2023-05-23  9:59 ` Chao Yu
2023-05-23 12:27   ` [f2fs-dev] [PATCH v2] " zangyangyang1 via Linux-f2fs-devel
2023-05-24  3:02     ` Chao Yu [this message]
2023-11-09 13:00     ` [f2fs-dev] [PATCH V2] libf2fs: Fix using uninitialized variables error in get_device_info() zangyangyang1 via Linux-f2fs-devel
2023-11-09 15:40       ` zangyangyang1 via Linux-f2fs-devel

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=4cbd654a-cbed-2acc-8fe5-898e534eb6fe@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=zangyangyang1@xiaomi.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;
as well as URLs for NNTP newsgroup(s).