linux-kernel - [PATCH 0/3] Fix boot problem with deferred meminit on machine with no node 0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1468008031-3848-1-git-send-email-mgorman@techsingularity.net>
Date:	Fri,  8 Jul 2016 21:00:28 +0100
From:	Mel Gorman <mgorman@...hsingularity.net>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Linux-MM <linux-mm@...ck.org>, LKML <linux-kernel@...r.kernel.org>,
	Mel Gorman <mgorman@...hsingularity.net>
Subject: [PATCH 0/3] Fix boot problem with deferred meminit on machine with no node 0

A machine with only node 1 was observed to crash very early in boot with
the following message

[    0.000000] BUG: unable to handle kernel paging request at 000000000002a3c8
[    0.000000] PGD 0
[    0.000000] Modules linked in:
[    0.000000] Hardware name: Supermicro H8DSP-8/H8DSP-8, BIOS 080011  06/30/2006
[    0.000000] task: ffffffff81c0d500 ti: ffffffff81c00000 task.ti: ffffffff81c00000
[    0.000000] RIP: 0010:[<ffffffff816dbd63>]  [<ffffffff816dbd63>] reserve_bootmem_region+0x6a/0xef
[    0.000000] RSP: 0000:ffffffff81c03eb0  EFLAGS: 00010086
[    0.000000] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[    0.000000] RDX: ffffffff81c03ec0 RSI: ffffffff81d205c0 RDI: ffffffff8213ee60
[    0.000000] R13: ffffea0000000000 R14: ffffea0000000020 R15: ffffea0000000020
[    0.000000] FS:  0000000000000000(0000) GS:ffff8800fba00000(0000) knlGS:0000000000000000
[    0.000000] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    0.000000] CR2: 000000000002a3c8 CR3: 0000000001c06000 CR4: 00000000000006b0
[    0.000000] Stack:
[    0.000000]  ffffffff81c03f00 0000000000000400 ffff8800fbfc3200 ffffffff81e2a2c0
[    0.000000]  ffffffff81c03fb0 ffffffff81c03f20 ffffffff81dadf7d ffffea0002000040
[    0.000000]  ffffea0000000000 0000000000000000 000000000000ffff 0000000000000001
[    0.000000] Call Trace:
[    0.000000]  [<ffffffff81dadf7d>] free_all_bootmem+0x4b/0x12a
[    0.000000]  [<ffffffff81d97122>] mem_init+0x70/0xa3
[    0.000000]  [<ffffffff81d78f21>] start_kernel+0x25b/0x49b

This series is the lowest-risk solution to the problem.

 mm/page_alloc.c | 17 +++--------------
 1 file changed, 3 insertions(+), 14 deletions(-)

-- 
2.6.4