linux-kernel - Re: CONFIG_HOLES_IN_ZONE and memory hot plug code on x86

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAE9FiQWhzZBGKyLicuw_J_d6t_CrmwTndkRvj+NC=6WZgpda-Q@mail.gmail.com>
Date:	Thu, 27 Aug 2015 22:20:47 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Steffen Persvold <sp@...ascale.com>
Cc:	x86 <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: CONFIG_HOLES_IN_ZONE and memory hot plug code on x86_64

On Fri, Jun 26, 2015 at 4:31 PM, Steffen Persvold <sp@...ascale.com> wrote:
> We’ve encountered an issue in a special case where we have a sparse E820 map [1].
>
> Basically the memory hotplug code is causing a “kernel paging request” BUG [2].

the trace does not look like hotplug path.

>
> By instrumenting the function register_mem_sect_under_node() in drivers/base/node.c we see that it is called two times with the same struct memory_block argument :
>
> [    1.901463] register_mem_sect_under_node: start = 80, end = 8f, nid = 0
> [    1.908129] register_mem_sect_under_node: start = 80, end = 8f, nid = 1

Can you post whole log with SRAT related info?

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/