From: Qian Cai <cai@lca.pw>
To: pasha.tatashin@oracle.com, mingo@kernel.org, mhocko@suse.com,
akpm@linux-foundation.org
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
hpa@zytor.com, mgorman@techsingularity.net, tglx@linutronix.de
Subject: kernel panic with page_owner=on
Date: Tue, 18 Dec 2018 17:31:25 -0500 [thread overview]
Message-ID: <1545172285.18411.26.camel@lca.pw> (raw)
CONFIG_DEBUG_VM_PGFLAGS=y
PAGE_OWNER=y
NODE_NOT_IN_PAGE_FLAGS=n
This seems due to f165b378bbd (mm: uninitialized struct page poisoning sanity
checking) shoots itself in the foot.
[ 11.917212] page:ffffea0004200000 is uninitialized and poisoned
[ 11.917220] raw: ffffffffffffffff ffffffffffffffff ffffffffffffffff
ffffffffffffffff
[ 11.921745] raw: ffffffffffffffff ffffffffffffffff ffffffffffffffff
ffffffffffffffff
[ 11.924523] page dumped because: VM_BUG_ON_PAGE(PagePoisoned(p))
[ 11.926498] page_owner info is not active (free page?)
[ 11.928234] ------------[ c-----
[ 12.329560] kernel BUG at include/linux/mm.h:990!
[ 12.337632] RIP: 0010:init_page_owner+0x486/0x520
[ 12.345238] RSP: 0000:ffffffff87c07d28 EFLAGS: 00010286
[ 12.346953] RAX: 0000000000000000 RBX: 0000000000108000 RCX: ffffffff85e5984c
[ 12.349253] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff87c07800
[ 12.351546] RBP: ffffffff87c07df8 R08: fffffbfff0fc0d41 R09: 0000000000000000
[ 12.353911] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000108200
[ 12.356186] R13: ffffea0004200000 R14: 0000000000280000 R15: ffffffffffffffff
[ 12.358532] FS: 0000000000000000(0000) GS:ffff8881eb600000(0000)
knlGS:0000000000000000
[ 12.361190] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 12.363065] CR2: ffff8882d7401000 CR3: 00000002d4214001 CR4: 00000000000606b0
[ 12.365434] Call Trace:
[ 12.366566] ? read_page_owner+0x470/0x470
[ 12.367944] ? kmemleak_not_leak+0x45/0x80
[ 12.369293] page_ext_init+0x233/0x23f
[ 12.370535] start_kernel+0x592/0x6b6
[ 12.371735]_cache_init+0xb/0xb
[ 12.773100] ? init_intel_microcode+0xd7/0xd7
[ 12.774614] ? cmdline_find_option_bool+0x82/0x1b0
[ 12.776221] x86_64_start_reserons+0x24/0x26
[ 12.877703] x86_64_start_kernel+0xf9/0x100
[ 12.879120] secondary_startup_64+0xb6/0xc0
At first,
start_kernel
setup_arch
pagetable_init
paging_init
sparse_init
sparse_init_nid
sparse_buffer_init
memblock_virt_alloc_try_nid_raw
It poisons all the allocated pages there.
memset(ptr, PAGE_POISON_PATTERN, size)
Later,
page_ext_init
invoke_init_callbacks
init_section_page_ext
init_page_owner
init_early_allocated_pages
init_zones_in_node
init_pages_in_zone
lookup_page_ext
page_to_nid
PF_POISONED_CHECK <--- panic here.
This because all allocated pages are not initialized until later.
init_pages_in_zone
__set_page_owner_handle
next reply other threads:[~2018-12-18 22:31 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 22:31 Qian Cai [this message]
2018-12-19 1:57 ` [PATCH] mm: skip checking poison pattern for page_to_nid() Qian Cai
2018-12-19 10:20 ` Michal Hocko
2018-12-19 12:46 ` Qian Cai
2018-12-20 6:03 ` [PATCH] mm/page_owner: fix for deferred struct page init Qian Cai
2018-12-20 9:22 ` Michal Hocko
2018-12-20 18:50 ` [PATCH v2] " Qian Cai
2018-12-20 20:31 ` [PATCH v3] " Qian Cai
2018-12-20 21:00 ` William Kucharski
2018-12-20 21:04 ` Qian Cai
2018-12-20 21:04 ` Qian Cai
2019-01-03 11:51 ` Michal Hocko
2019-01-03 16:38 ` Qian Cai
2019-01-03 16:59 ` Michal Hocko
2019-01-03 17:38 ` Qian Cai
2019-01-03 19:07 ` Michal Hocko
2019-01-03 19:53 ` Qian Cai
2019-01-03 20:22 ` Michal Hocko
2019-01-03 22:22 ` Qian Cai
2019-01-04 13:09 ` Michal Hocko
2019-01-04 15:01 ` Qian Cai
2019-01-04 15:17 ` Michal Hocko
2019-01-04 15:25 ` Qian Cai
2019-01-04 15:32 ` Michal Hocko
2019-01-04 20:18 ` Qian Cai
2019-01-07 18:43 ` Michal Hocko
2019-01-08 1:53 ` Qian Cai
2019-01-08 8:20 ` Michal Hocko
2019-01-08 13:19 ` Qian Cai
2019-01-08 13:19 ` Qian Cai
2019-01-08 22:02 ` Andrew Morton
2019-01-08 22:13 ` Qian Cai
2019-01-08 22:40 ` Michal Hocko
2019-01-09 7:34 ` [PATCH v2] " Michal Hocko
2019-01-15 20:28 ` [PATCH] Revert "mm: use early_pfn_to_nid in page_ext_init" Qian Cai
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=1545172285.18411.26.camel@lca.pw \
--to=cai@lca.pw \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=pasha.tatashin@oracle.com \
--cc=tglx@linutronix.de \
/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