linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ram Pai <linuxram@us.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] powerpc/mm: Fix crashes with PUD level hugetlb config
Date: Sat, 10 Feb 2018 08:50:10 -0800	[thread overview]
Message-ID: <20180210165010.GC5559@ram.oc3035372033.ibm.com> (raw)
In-Reply-To: <87o9kxfa7d.fsf@linux.vnet.ibm.com>

On Sat, Feb 10, 2018 at 03:17:02PM +0530, Aneesh Kumar K.V wrote:
> Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> writes:
> 
> > "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> writes:
> >
> >> To support memory keys, we moved the hash pte slot information to the second
> >> half of the page table. This was ok with PTE entries at level 4 and level 3.
> >> We already allocate larger page table pages at those level to accomodate extra
> >> details. For level 4 we already have the extra space which was used to track
> >> 4k hash page table entry details and at pmd level the extra space was allocated
> >> to track the THP details.
> >>
> >> With hugetlbfs PTE, we used this extra space at the PMD level to store the
> >> slot details. But we also support hugetlbfs PTE at PUD leve and PUD level page
> >> didn't allocate extra space. This resulted in memory corruption.
> >>
> >> Fix this by allocating extra space at PUD level when HUGETLB is enabled. We
> >> may need further changes to allocate larger space at PMD level when we enable
> >> HUGETLB. That will be done in next patch.
> >>
> >> Fixes:bf9a95f9a6481bc6e(" powerpc: Free up four 64K PTE bits in 64K backed HPTE pages")
> >>
> >> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> >
> > Another fix, I still get random memory corruption with hugetlb test with
> > 16G hugepage config.
> 
> Another one. I am not sure whether we really want this in this form. But
> with this tests are running fine.
> 
> -aneesh
> 
> commit 658fe8c310a913e69e5bc9a40d4c28a3b88d5c08
> Author: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> Date:   Sat Feb 10 13:17:34 2018 +0530
> 
>     powerpc/mm/hash64: memset the pagetable pages on allocation.
>     
>     Now that we are using second half of the table to store slot details and we
>     don't clear them in the huge_pte_get_and_clear, we need to make sure we zero
>     out the range on allocation. This done some extra work because the first half
>     of the table is cleared by huge_pte_get_and_clear and memset in this patch
>     zero-out the full table page.
>     
>     We need to do this for pgd and pud because both get allocated from the same slab
>     cache.

Do we need to zero pgd aswell to resolve your corruption? pud is not
sufficient? Or was it done to avoid issues in the future in case pgd
is used as the leaf; possibly for Terra_huge_pages?

RP

  reply	other threads:[~2018-02-10 16:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 10:34 [PATCH 1/2] powerpc/mm: Fix crashes with PUD level hugetlb config Aneesh Kumar K.V
2018-02-08 10:34 ` [PATCH 2/2] powerpc/mm/hash64: Allocate larger PMD table if hugetlb config is enabled Aneesh Kumar K.V
2018-02-08 15:16 ` [PATCH 1/2] powerpc/mm: Fix crashes with PUD level hugetlb config Aneesh Kumar K.V
2018-02-08 19:29   ` Ram Pai
2018-02-09 15:31     ` Aneesh Kumar K.V
2018-02-10  9:47   ` Aneesh Kumar K.V
2018-02-10 16:50     ` Ram Pai [this message]
2018-02-10 17:14       ` Aneesh Kumar K.V
2018-02-08 19:22 ` Ram Pai
2018-02-09 15:30   ` Aneesh Kumar K.V

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=20180210165010.GC5559@ram.oc3035372033.ibm.com \
    --to=linuxram@us.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.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).