From: David Laight <David.Laight@ACULAB.COM>
To: "'cgel.zte@gmail.com'" <cgel.zte@gmail.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Changcheng Deng <deng.changcheng@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>
Subject: RE: [PATCH] mm/page_alloc.c: Use div64_ul instead of do_div
Date: Fri, 7 Jan 2022 09:15:54 +0000 [thread overview]
Message-ID: <665a758a3bd5421ea7cf9c01d154f718@AcuMS.aculab.com> (raw)
In-Reply-To: <20220107021751.621522-1-deng.changcheng@zte.com.cn>
From: cgel.zte@gmail.com
> Sent: 07 January 2022 02:18
>
> do_div() does a 64-by-32 division. Here the divisor is an unsigned long
> which on some platforms is 64 bit wide. So use div64_ul instead of do_div
> to avoid a possible truncation.
You really need to check the domain of the divisor, not its type.
Just because the type is 64 bits doesn't mean that the value can be
anywhere near even 32 bits.
David
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Changcheng Deng <deng.changcheng@zte.com.cn>
> ---
> mm/page_alloc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 8dd6399bafb5..60469b616ac1 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -8431,7 +8431,7 @@ static void __setup_per_zone_wmarks(void)
>
> spin_lock_irqsave(&zone->lock, flags);
> tmp = (u64)pages_min * zone_managed_pages(zone);
> - do_div(tmp, lowmem_pages);
> + tmp = div64_ul(tmp, lowmem_pages);
> if (is_highmem(zone)) {
> /*
> * __GFP_HIGH and PF_MEMALLOC allocations usually don't
> @@ -8804,7 +8804,7 @@ void *__init alloc_large_system_hash(const char *tablename,
> /* limit allocation size to 1/16 total memory by default */
> if (max == 0) {
> max = ((unsigned long long)nr_all_pages << PAGE_SHIFT) >> 4;
> - do_div(max, bucketsize);
> + max = div64_ul(max, bucketsize);
> }
> max = min(max, 0x80000000ULL);
>
> --
> 2.25.1
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
prev parent reply other threads:[~2022-01-07 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 2:17 cgel.zte
2022-01-07 9:15 ` David Laight [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=665a758a3bd5421ea7cf9c01d154f718@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=cgel.zte@gmail.com \
--cc=deng.changcheng@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=zealci@zte.com.cn \
/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