linux-kernel - Re: [PATCH v2 0/3] support for broken memory modules (BadRAM)

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:	Fri, 24 Jun 2011 16:56:12 +0000
From:	Rick van Rein <rick@...rein.org>
To:	"Luck, Tony" <tony.luck@...el.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>, Rick van Rein <rick@...rein.org>,
	Craig Bergstrom <craigb@...gle.com>,
	Andi Kleen <andi@...stfloor.org>,
	Stefan Assmann <sassmann@...nic.de>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"mingo@...e.hu" <mingo@...e.hu>,
	"rdunlap@...otime.net" <rdunlap@...otime.net>
Subject: Re: [PATCH v2 0/3] support for broken memory modules (BadRAM)

Hello,

> Does it scale? [...] Perhaps we may end up with a composite solution. 

If I had my way, there would be an extension to the e820 format to allow
the BadRAM patterns to be specified.  Since the extension with bad page
information is specific to boot loader interaction, this would work in
exactly those cases that are covered by the current situation.

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