From: Alison Schofield <alison.schofield@intel.com>
To: Quanquan Cao <caoqq@fujitsu.com>
Cc: dave.jiang@intel.com, vishal.l.verma@intel.com,
linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev
Subject: Re: [PATCH] cxl/region:Fix overflow issue in alloc_hpa()
Date: Fri, 26 Jan 2024 13:47:36 -0800 [thread overview]
Message-ID: <ZbQoeIrWzzTPdqqF@aschofie-mobl2> (raw)
In-Reply-To: <20240124091527.8469-1-caoqq@fujitsu.com>
On Wed, Jan 24, 2024 at 05:15:26PM +0800, Quanquan Cao wrote:
> Creating a region with 16 memory devices caused a problem. The div_u64_rem
> function, used for dividing an unsigned 64-bit number by a 32-bit one,
> faced an issue when SZ_256M * p->interleave_ways. The result surpassed
> the maximum limit of the 32-bit divisor (4G), leading to an overflow
> and a remainder of 0.
> note: At this point, p->interleave_ways is 16, meaning 16 * 256M = 4G
>
> To fix this issue, I replaced the div_u64_rem function with div64_u64_rem
> and adjusted the type of the remainder.
Good find! Should this have a Fixes Tag?
Reviewed-by: Alison Schofield <alison.schofield@intel.com>
>
> Signed-off-by: Quanquan Cao <caoqq@fujitsu.com>
> ---
> drivers/cxl/core/region.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
> index 0f05692bfec3..ce0e2d82bb2b 100644
> --- a/drivers/cxl/core/region.c
> +++ b/drivers/cxl/core/region.c
> @@ -525,7 +525,7 @@ static int alloc_hpa(struct cxl_region *cxlr, resource_size_t size)
> struct cxl_root_decoder *cxlrd = to_cxl_root_decoder(cxlr->dev.parent);
> struct cxl_region_params *p = &cxlr->params;
> struct resource *res;
> - u32 remainder = 0;
> + u64 remainder = 0;
>
> lockdep_assert_held_write(&cxl_region_rwsem);
>
> @@ -545,7 +545,7 @@ static int alloc_hpa(struct cxl_region *cxlr, resource_size_t size)
> (cxlr->mode == CXL_DECODER_PMEM && uuid_is_null(&p->uuid)))
> return -ENXIO;
>
> - div_u64_rem(size, SZ_256M * p->interleave_ways, &remainder);
> + div64_u64_rem(size, (u64)SZ_256M * p->interleave_ways, &remainder);
> if (remainder)
> return -EINVAL;
>
> --
> 2.43.0
>
>
prev parent reply other threads:[~2024-01-26 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 9:15 [PATCH] cxl/region:Fix overflow issue in alloc_hpa() Quanquan Cao
2024-01-24 23:59 ` fan
2024-01-25 0:02 ` Dave Jiang
2024-01-26 17:42 ` Jonathan Cameron
2024-01-29 2:22 ` Cao, Quanquan/曹 全全
2024-01-26 21:47 ` Alison Schofield [this message]
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=ZbQoeIrWzzTPdqqF@aschofie-mobl2 \
--to=alison.schofield@intel.com \
--cc=caoqq@fujitsu.com \
--cc=dave.jiang@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.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