All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org
Cc: bugzilla-daemon@bugzilla.kernel.org, kernel@bluematt.me
Subject: Re: [Bug 202149] New: NULL Pointer Dereference in __split_huge_pmd on PPC64LE
Date: Tue, 08 Jan 2019 12:45:08 +0530	[thread overview]
Message-ID: <87ef9nk4cj.fsf@linux.ibm.com> (raw)
In-Reply-To: <20190104170459.c8c7fa57ba9bc8a69dee5666@linux-foundation.org>

Andrew Morton <akpm@linux-foundation.org> writes:

> (switched to email.  Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Fri, 04 Jan 2019 22:49:52 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:
>
>> https://bugzilla.kernel.org/show_bug.cgi?id=202149
>> 
>>             Bug ID: 202149
>>            Summary: NULL Pointer Dereference in __split_huge_pmd on
>>                     PPC64LE
>
> I think that trace is pointing at the ppc-specific
> pgtable_trans_huge_withdraw()?
>

That is correct. 

Matt,
Can you share the .config used for the kernel. Does this happen only
with 4K page size ?

-aneesh


  reply	other threads:[~2019-01-08  7:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-202149-27@https.bugzilla.kernel.org/>
2019-01-05  1:04 ` [Bug 202149] New: NULL Pointer Dereference in __split_huge_pmd on PPC64LE Andrew Morton
2019-01-08  7:15   ` Aneesh Kumar K.V [this message]
2019-01-08 19:17     ` Matt Corallo
2019-01-09 11:50       ` Aneesh Kumar K.V
2019-01-09 13:38         ` Matt Corallo
2019-01-09 13:38           ` Matt Corallo
2019-01-21 12:35           ` Aneesh Kumar K.V
2019-01-21 12:35             ` Aneesh Kumar K.V
2019-01-21 12:35             ` Aneesh Kumar K.V
2019-02-14 20:17             ` Matt Corallo
2019-02-14 20:17               ` Matt Corallo
2019-02-15  3:58               ` 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=87ef9nk4cj.fsf@linux.ibm.com \
    --to=aneesh.kumar@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kernel@bluematt.me \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.