linux-kernel - Re: [RESEND PATCH] mm: clear N_HIGH_MEMORY map before se set it again -v2

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 04 Jun 2009 09:48:20 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Christoph Lameter <cl@...ux-foundation.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>, mingo@...e.hu,
	tglx@...utronix.de, hpa@...or.com, mel@....ul.ie,
	suresh.b.siddha@...el.com, linux-kernel@...r.kernel.org,
	viro@...iv.linux.org.uk, rusty@...tcorp.com.au, steiner@....com,
	rientjes@...gle.com
Subject: Re: [RESEND PATCH] mm: clear N_HIGH_MEMORY map before se set it again
 -v2

Christoph Lameter wrote:
> Ok. The N_HIGH_MEMORY bit is set for all onlines nodes in a loop
> that follows the code you modified. The patch insures that bits do not
> remain set that earlier arch / core code may have set.
> 
> Could you make the description clearer?
> 

how about

Subject: [PATCH] mm: clear N_HIGH_MEMORY map before se set it again -v3

in case some system strange SRAT table. some kind of small range form some node
or with mem= boot option etc. that node will not be onlined.  
In the early checking, the bit in node_states[N_HIGH_MEMORY] for the
node is set even that node has less RAM like 1M.

The N_HIGH_MEMORY bit is set for all onlines nodes in a loop that follows the 
code that is modified. The patch insures that bits do not remain set that 
earlier arch / core code may have set.

for 64bit N_HIGH_MEMORY == N_NORMAL_MEMORY, so that works for 64 bit too

v3: update description according to Christoph

--
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/