From: mpatocka@redhat.com (Mikulas Patocka)
To: linux-arm-kernel@lists.infradead.org
Subject: A crash on ARM64 in move_freepages_block due to uninitialized pages in reserved memory
Date: Thu, 23 Aug 2018 10:34:38 -0400 (EDT) [thread overview]
Message-ID: <alpine.LRH.2.02.1808231017570.4129@file01.intranet.prod.int.rdu2.redhat.com> (raw)
In-Reply-To: <777276b8-9cd6-da4b-d1d9-c60f96a58122@microsoft.com>
On Thu, 23 Aug 2018, Pasha Tatashin wrote:
> On 8/23/18 7:23 AM, Michal Hocko wrote:
> > On Thu 23-08-18 07:16:34, Mikulas Patocka wrote:
> >>
> >>
> >> On Thu, 23 Aug 2018, Michal Hocko wrote:
> >>
> >>> On Thu 23-08-18 07:02:37, Mikulas Patocka wrote:
> >>> [...]
> >>>> This crash is not from -ENOENT. It crashes because page->compound_head is
> >>>> 0xffffffffffffffff (see below).
> >>>>
> >>>> If I enable CONFIG_DEBUG_VM, I also get VM_BUG.
> >>>
> >>> This smells like the struct page is not initialized properly. How is
> >>> this memory range added? I mean is it brought up by the memory hotplug
> >>> or during the boot?
>
> I believe it is due to uninitialized struct pages. Mikulas, could you
> please provide config file, and also the full console output.
>
> Please make sure that you have:
> CONFIG_DEBUG_VM=y
> CONFIG_ARCH_HAS_DEBUG_VIRTUAL=y
>
> I wonder what kind of struct page memory layout is used, and also if
> deferred struct pages are enabled or not.
I uploaded configs and console logs (for the real hardware and for the
virtual machine) here:
http://people.redhat.com/~mpatocka/testcases/arm64-config/
The virtual machine was running the lvm2 testsuite while the crash
happened.
> Have you tried bisecting the problem?
I may try some old kernel in the virtual machine to test if the bug
happens on it.
> Thank you,
> Pavel
Mikulas
next prev parent reply other threads:[~2018-08-23 14:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 19:44 A crash on ARM64 in move_freepages_block due to uninitialized pages in reserved memory Mikulas Patocka
2018-08-21 10:44 ` Michal Hocko
2018-08-21 12:58 ` James Morse
2018-08-23 11:02 ` Mikulas Patocka
2018-08-23 11:10 ` Michal Hocko
2018-08-23 11:16 ` Mikulas Patocka
2018-08-23 11:23 ` Michal Hocko
2018-08-23 13:13 ` Pasha Tatashin
2018-08-23 13:14 ` Pasha Tatashin
2018-08-23 14:34 ` Mikulas Patocka [this message]
2018-08-23 14:06 ` James Morse
2018-08-24 11:41 ` Michal Hocko
2018-08-29 17:37 ` James Morse
2018-08-30 15:58 ` Mikulas Patocka
2018-08-30 16:11 ` Will Deacon
2018-08-30 16:25 ` James Morse
2018-09-03 19:33 ` Michal Hocko
2018-09-07 17:47 ` James Morse
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=alpine.LRH.2.02.1808231017570.4129@file01.intranet.prod.int.rdu2.redhat.com \
--to=mpatocka@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).