linux-kernel - Re: [PATCH Bug fix] acpi, movablemem_map: node0 should always be unhotpluggable when using SRAT.

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]

Date:	Wed, 30 Jan 2013 17:05:09 +0800
From:	Tang Chen <tangchen@...fujitsu.com>
To:	David Rientjes <rientjes@...gle.com>
CC:	akpm@...ux-foundation.org, jiang.liu@...wei.com,
	wujianguo@...wei.com, hpa@...or.com, wency@...fujitsu.com,
	laijs@...fujitsu.com, linfeng@...fujitsu.com, yinghai@...nel.org,
	isimatu.yasuaki@...fujitsu.com, rob@...dley.net,
	kosaki.motohiro@...fujitsu.com, minchan.kim@...il.com,
	mgorman@...e.de, guz.fnst@...fujitsu.com, rusty@...tcorp.com.au,
	lliubbo@...il.com, jaegeuk.hanse@...il.com, tony.luck@...el.com,
	glommer@...allels.com, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org
Subject: Re: [PATCH Bug fix] acpi, movablemem_map: node0 should always be
 unhotpluggable when using SRAT.

On 01/30/2013 04:50 PM, David Rientjes wrote:
> On Wed, 30 Jan 2013, Tang Chen wrote:
>
>> When using movablemem_map=acpi, always set node0 as unhotpluggable, otherwise
>> if all the memory is hotpluggable, the kernel will fail to boot.
>>
>> When using movablemem_map=nn[KMG]@ss[KMG], we don't stop users specifying
>> node0 as hotpluggable, and ignore all the info in SRAT, so that this option
>> can be used as a workaround of firmware bugs.
>>
>
> Could you elaborate on the failure you're seeing?
>
> I've booted the kernel many times without memory on a node 0.
>

Hi David,

The failure I'm trying to fix is that if all the memory is hotpluggable, 
and user
specified movablemem_map, my code will set all the memory as 
ZONE_MOVABLE, and kernel
will fail to allocate any memory, and it will fail to boot.

But I'm sorry if I didn't answer your question. :)

Are you saying your memory is not on node0, and your physical address
0x0 is not on node0 ? And your /sys fs don't have a node0 interface, it is
node1 or something else ?

If so, I think I'd better find another way to fix this problem because 
node0 may not be
the first node on the system.

Thanks. :)
--
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/