linux-kernel - Re: [PATCH 2.6.24] mm: BadRAM support for broken memory

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]

Message-ID: <47D269AB.2010306@zytor.com>
Date:	Sat, 08 Mar 2008 11:25:47 +0100
From:	"H. Peter Anvin" <hpa@...or.com>
To:	KOSAKI Motohiro <m-kosaki@...es.dti.ne.jp>
CC:	Pavel Machek <pavel@....cz>, Rick van Rein <rick@...rein.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.24] mm: BadRAM support for broken memory

KOSAKI Motohiro wrote:
> Hi!
> 
>>  > This is the latest version of the BadRAM patch, which makes it possible to
>>  > run Linux on broken memory.  The patch supports the use of a lesser grade
>>  > of memory, which could be marketed more cheaply and which would thereby
>>  > decrease the environmental stress caused by the process of (memory) chip
>>  > manufacturing.
>>
>>  What is wrong with mem=exactmap?
> 
> Agghh,
> I had forgotten that.
> 
> you are right, may be.

More importantly:

	memmap=<size>$<len>

already allows you to knock arbitrary holes in the memory map.

	-hpa

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