[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f3a2db67-f7b7-1bb7-340f-24806a999192@oracle.com>
Date: Thu, 14 May 2020 09:31:02 -0700
From: Mike Kravetz <mike.kravetz@...cle.com>
To: Michal Hocko <mhocko@...nel.org>,
Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: linux- stable <stable@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>, Hugh Dickins <hughd@...gle.com>,
Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
Andrea Arcangeli <aarcange@...hat.com>,
"Kirill A.Shutemov" <kirill.shutemov@...ux.intel.com>,
Davidlohr Bueso <dave@...olabs.net>,
Prakash Sangappa <prakash.sangappa@...cle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
lkft-triage@...ts.linaro.org, Arnd Bergmann <arnd@...db.de>,
John Stultz <john.stultz@...aro.org>
Subject: Re: stable-rc 5.4: libhugetlbfs fallocate_stress.sh: Unable to handle
kernel paging request at virtual address ffff00006772f000
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
Powered by blists - more mailing lists