From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Matt Corallo <kernel@bluematt.me>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org
Cc: bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 202149] New: NULL Pointer Dereference in __split_huge_pmd on PPC64LE
Date: Wed, 09 Jan 2019 17:20:40 +0530 [thread overview]
Message-ID: <8736q2jbhr.fsf@linux.ibm.com> (raw)
In-Reply-To: <ed4bea40-cf9e-89a1-f99a-3dbd6249847f@bluematt.me>
Matt Corallo <kernel@bluematt.me> writes:
> .config follows. I have not tested with 64K pages as, sadly, I have a
> large BTRFS volume that was formatted on x86, and am thus stuck with 4K
> pages. Note that this is roughly the Debian kernel, so it has whatever
> patches Debian defaults to applying, a list of which follows.
>
What is the test you are running? I tried a 4K page size config on P9. I
am running ltp test suite there. Also tried few thp memremap tests.
Nothing hit that.
root@:~/tests/ltp/testcases/kernel/mem/thp# getconf PAGESIZE
4096
root@ltc-boston123:~/tests/ltp/testcases/kernel/mem/thp# grep thp /proc/vmstat
thp_fault_alloc 641141
thp_fault_fallback 0
thp_collapse_alloc 90
thp_collapse_alloc_failed 0
thp_file_alloc 0
thp_file_mapped 0
thp_split_page 1
thp_split_page_failed 0
thp_deferred_split_page 641150
thp_split_pmd 24
thp_zero_page_alloc 1
thp_zero_page_alloc_failed 0
thp_swpout 0
thp_swpout_fallback 0
root@:~/tests/ltp/testcases/kernel/mem/thp#
-aneesh
next prev parent reply other threads:[~2019-01-09 11:52 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
2019-01-08 19:17 ` Matt Corallo
2019-01-09 11:50 ` Aneesh Kumar K.V [this message]
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=8736q2jbhr.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.