From: patchwork-bot+f2fs@kernel.org
To: Nikita Zhandarovich <n.zhandarovich@fintech.ru>
Cc: lvc-project@linuxtesting.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net,
jaegeuk@kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: avoid potential int overflow in sanity_check_area_boundary()
Date: Mon, 05 Aug 2024 23:30:52 +0000 [thread overview]
Message-ID: <172290065201.2803.7144786550538079483.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240724175158.11928-1-n.zhandarovich@fintech.ru>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 24 Jul 2024 10:51:58 -0700 you wrote:
> While calculating the end addresses of main area and segment 0, u32
> may be not enough to hold the result without the danger of int
> overflow.
>
> Just in case, play it safe and cast one of the operands to a
> wider type (u64).
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: avoid potential int overflow in sanity_check_area_boundary()
https://git.kernel.org/jaegeuk/f2fs/c/50438dbc483c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Nikita Zhandarovich <n.zhandarovich@fintech.ru>
Cc: jaegeuk@kernel.org, chao@kernel.org,
lvc-project@linuxtesting.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: avoid potential int overflow in sanity_check_area_boundary()
Date: Mon, 05 Aug 2024 23:30:52 +0000 [thread overview]
Message-ID: <172290065201.2803.7144786550538079483.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240724175158.11928-1-n.zhandarovich@fintech.ru>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 24 Jul 2024 10:51:58 -0700 you wrote:
> While calculating the end addresses of main area and segment 0, u32
> may be not enough to hold the result without the danger of int
> overflow.
>
> Just in case, play it safe and cast one of the operands to a
> wider type (u64).
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: avoid potential int overflow in sanity_check_area_boundary()
https://git.kernel.org/jaegeuk/f2fs/c/50438dbc483c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-08-05 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 17:51 [f2fs-dev] [PATCH] f2fs: avoid potential int overflow in sanity_check_area_boundary() Nikita Zhandarovich
2024-07-24 17:51 ` Nikita Zhandarovich
2024-07-25 3:26 ` [f2fs-dev] " Chao Yu
2024-07-25 3:26 ` Chao Yu
2024-08-05 23:30 ` patchwork-bot+f2fs [this message]
2024-08-05 23:30 ` [f2fs-dev] " patchwork-bot+f2fs
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=172290065201.2803.7144786550538079483.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=n.zhandarovich@fintech.ru \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.