From: Rui Teng <rui.teng@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Boqun Feng <boqun.feng@gmail.com>,
jia he <hejianet@linux.vnet.ibm.com>
Subject: Re: [PATCH] powerpc/mm: fix a hardcode on memory boundary checking
Date: Mon, 6 Feb 2017 10:50:21 +0800 [thread overview]
Message-ID: <a97db3cd-a756-390c-505e-819718b64904@linux.vnet.ibm.com> (raw)
In-Reply-To: <877f5bvbjm.fsf@concordia.ellerman.id.au>
On 31/01/2017 5:11 PM, Michael Ellerman wrote:
> Rui Teng <rui.teng@linux.vnet.ibm.com> writes:
>
>> The offset of hugepage block will not be 16G, if the expected
>> page is more than one. Calculate the totol size instead of the
>> hardcode value.
>
> I assume you found this by code inspection and not by triggering an
> actual bug?
Yes, I found this problem only by code inspection. We were finding the
ways to enable 16G huge page besides changing the device tree. For
example, provide a new interface to set these size and pages parameters.
So that I think it may cause problem here.
>
> cheers
>
>> diff --git a/arch/powerpc/mm/hash_utils_64.c b/arch/powerpc/mm/hash_utils_64.c
>> index 8033493..b829f8e 100644
>> --- a/arch/powerpc/mm/hash_utils_64.c
>> +++ b/arch/powerpc/mm/hash_utils_64.c
>> @@ -506,7 +506,7 @@ static int __init htab_dt_scan_hugepage_blocks(unsigned long node,
>> printk(KERN_INFO "Huge page(16GB) memory: "
>> "addr = 0x%lX size = 0x%lX pages = %d\n",
>> phys_addr, block_size, expected_pages);
>> - if (phys_addr + (16 * GB) <= memblock_end_of_DRAM()) {
>> + if (phys_addr + block_size * expected_pages <= memblock_end_of_DRAM()) {
>> memblock_reserve(phys_addr, block_size * expected_pages);
>> add_gpage(phys_addr, block_size, expected_pages);
>> }
>> --
>> 2.9.0
>
next prev parent reply other threads:[~2017-02-06 2:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 9:09 [PATCH] powerpc/mm: fix a hardcode on memory boundary checking Rui Teng
2017-01-31 9:11 ` Michael Ellerman
2017-02-06 2:50 ` Rui Teng [this message]
2017-07-05 4:45 ` Anshuman Khandual
2017-08-07 10:41 ` Michael Ellerman
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=a97db3cd-a756-390c-505e-819718b64904@linux.vnet.ibm.com \
--to=rui.teng@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=boqun.feng@gmail.com \
--cc=hejianet@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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;
as well as URLs for NNTP newsgroup(s).