From: David Laight <David.Laight@ACULAB.COM>
To: 'Andrew Morton' <akpm@linux-foundation.org>, Wang Ming <machel@vivo.com>
Cc: Mike Rapoport <rppt@kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"opensource.kernel@vivo.com" <opensource.kernel@vivo.com>
Subject: RE: [PATCH v1] mm:Using div64_ul replaces do_div() function
Date: Tue, 20 Jun 2023 10:41:41 +0000 [thread overview]
Message-ID: <5c04998fb225430e8e4966cc95f8a0ea@AcuMS.aculab.com> (raw)
In-Reply-To: <20230616125219.dc2346534d6f279a7527c0b0@linux-foundation.org>
From: Andrew Morton
> Sent: 16 June 2023 20:52
>
> On Thu, 15 Jun 2023 15:51:14 +0800 Wang Ming <machel@vivo.com> wrote:
>
> > Fix the following coccicheck warning:
> >
> > mm/mm_init.c:2492:2-8: WARNING: do_div() does a
> > 64-by-32 division, please consider using div64_ul instead.
>
> I guess coccicheck was fooled by the incorrect comment over do_div().
> do_div() returns an unsigned long.
IIRC do_div() does an in-place update, but div64_ul() returns the result.
So the 'fixed' code is entirely broken.
The coccicheck message should really be 'check the domain/type of the divisor'.
> alloc_large_system_hash() should be using a u64 for `max'. Nobody uses
> unsigned long long any more.
Probably makes no difference.
The issue is with 'buckesize' - probably 'long' so 64bit on 64bit systems.
I guess 'max' can overflow 'long' on 32bit PAE.
Although using min(nr_all_pages, 0x80000000UL >> PAGE_SHIFT >> 4)
and doing everything as 'unsigned long' might be better.
David
>
> > --- a/mm/mm_init.c
> > +++ b/mm/mm_init.c
> > @@ -2508,7 +2508,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);
> > + div64_ul(max, bucketsize);
> > }
> > max = min(max, 0x80000000ULL);
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
prev parent reply other threads:[~2023-06-20 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230615075127.6832-1-machel@vivo.com>
2023-06-16 19:52 ` Andrew Morton
2023-06-20 10:41 ` 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=5c04998fb225430e8e4966cc95f8a0ea@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=machel@vivo.com \
--cc=opensource.kernel@vivo.com \
--cc=rppt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox