From: Mike Kravetz <mike.kravetz@oracle.com>
To: Michal Hocko <mhocko@kernel.org>,
Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux- stable <stable@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Hugh Dickins <hughd@google.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Andrea Arcangeli <aarcange@redhat.com>,
"Kirill A.Shutemov" <kirill.shutemov@linux.intel.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Prakash Sangappa <prakash.sangappa@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
lkft-triage@lists.linaro.org, Arnd Bergmann <arnd@arndb.de>,
John Stultz <john.stultz@linaro.org>
Subject: Re: stable-rc 5.4: libhugetlbfs fallocate_stress.sh: Unable to handle kernel paging request at virtual address ffff00006772f000
Date: Thu, 14 May 2020 09:31:02 -0700 [thread overview]
Message-ID: <f3a2db67-f7b7-1bb7-340f-24806a999192@oracle.com> (raw)
In-Reply-To: <20200514064039.GY29153@dhcp22.suse.cz>
On 5/13/20 11:40 PM, Michal Hocko wrote:
> On Wed 13-05-20 23:11:40, Naresh Kamboju wrote:
>> While running libhugetlbfs fallocate_stress.sh on stable-rc 5.4 branch kernel
>> on arm64 hikey device. The following kernel Internal error: Oops:
>> crash dump noticed.
>
> Is the same problem reproducible on vanilla 5.4 without any stable
> patches?
>
Or, an earlier version of 5.4-stable? Nothing in the changelog for 5.4.41
looks related to this issue. There was an arm specific hugetlb change
"arm64: hugetlb: avoid potential NULL dereference", but that is pretty
straight forward.
I'm guessing this may not reproduce easily. To help reproduce, you could
change the
#define FALLOCATE_ITERATIONS 100000
in .../libhugetlbfs/tests/fallocate_stress.c to a larger number to force
the stress test to run longer.
--
Mike Kravetz
next prev parent reply other threads:[~2020-05-14 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 17:41 Naresh Kamboju
2020-05-14 6:40 ` Michal Hocko
2020-05-14 16:31 ` Mike Kravetz [this message]
2020-06-10 7:08 ` Naresh Kamboju
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=f3a2db67-f7b7-1bb7-340f-24806a999192@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=arnd@arndb.de \
--cc=dave@stgolabs.net \
--cc=hughd@google.com \
--cc=john.stultz@linaro.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mhocko@kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=naresh.kamboju@linaro.org \
--cc=prakash.sangappa@oracle.com \
--cc=stable@vger.kernel.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