From: Michael Bringmann <mwb@linux.ibm.com>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: Gustavo Walbon <gwalbon@linux.ibm.com>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] Fix display of Maximum Memory
Date: Wed, 15 Jan 2020 08:30:02 -0600 [thread overview]
Message-ID: <eb6c4171-09b3-b8f0-6219-38757da6fc3b@linux.ibm.com> (raw)
In-Reply-To: <41380afd-05f5-f36f-c857-041243c73ee3@c-s.fr>
On 1/14/20 11:41 PM, Christophe Leroy wrote:
>
>
> Le 14/01/2020 à 22:07, Michael Bringmann a écrit :
>> Correct overflow problem in calculation+display of Maximum Memory
>> value to syscfg where 32bits is insufficient.
>>
>> Signed-off-by: Michael Bringmann <mwb@linux.ibm.com>
>> ---
>> arch/powerpc/platforms/pseries/lparcfg.c | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/powerpc/platforms/pseries/lparcfg.c b/arch/powerpc/platforms/pseries/lparcfg.c
>> index 4ee2594..183aeb7 100644
>> --- a/arch/powerpc/platforms/pseries/lparcfg.c
>> +++ b/arch/powerpc/platforms/pseries/lparcfg.c
>> @@ -435,12 +435,12 @@ static void parse_em_data(struct seq_file *m)
>>
>> static void maxmem_data(struct seq_file *m)
>> {
>> - unsigned long maxmem = 0;
>> + unsigned long long maxmem = 0;
>
> What about using u64 instead, for readability ?
Okay.
>
>>
>> - maxmem += drmem_info->n_lmbs * drmem_info->lmb_size;
>> - maxmem += hugetlb_total_pages() * PAGE_SIZE;
>> + maxmem += (unsigned long long)drmem_info->n_lmbs * (unsigned long long)drmem_info->lmb_size;
>
> This line is likely too long. You only need to cast one of the two operants to force a 64 bits multiply. And using u64 would shorten the line.
>
> Can both multiplications overflow ?
Yes.
>
> Christophe
>
>> + maxmem += (unsigned long long)hugetlb_total_pages() * (unsigned long long)PAGE_SIZE;
>>
>> - seq_printf(m, "MaxMem=%ld\n", maxmem);
>> + seq_printf(m, "MaxMem=%llu\n", maxmem);
>> }
>>
>> static int pseries_lparcfg_data(struct seq_file *m, void *v)
>>
>
Thanks.
--
Michael W. Bringmann
Linux Technology Center
IBM Corporation
Tie-Line 363-5196
External: (512) 286-5196
Cell: (512) 466-0650
mwb@linux.ibm.com
prev parent reply other threads:[~2020-01-15 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 21:07 Michael Bringmann
2020-01-15 5:41 ` Christophe Leroy
2020-01-15 14:30 ` Michael Bringmann [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=eb6c4171-09b3-b8f0-6219-38757da6fc3b@linux.ibm.com \
--to=mwb@linux.ibm.com \
--cc=christophe.leroy@c-s.fr \
--cc=gwalbon@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®