linux-kernel - Re: [PATCH] EFI: Only set regions uncacheable if they support it

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:	Thu, 15 Mar 2012 14:24:46 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux-kernel@...r.kernel.org, x86@...nel.org,
	matt.fleming@...el.com
Subject: Re: [PATCH] EFI: Only set regions uncacheable if they support it

On Thu, Mar 15, 2012 at 07:17:56AM -0700, H. Peter Anvin wrote:
> On 03/15/2012 07:07 AM, Matthew Garrett wrote:
> > 
> > I have a report of a system that fails to boot with an MCE during EFI 
> > setup. The memory range is marked reserved and claims not to support any 
> > caching type, which I think probably translates as "Don't do anything to 
> > this region ever".
> > 
> 
> In other words, "don't map me"... not something we really support at the
> moment, but perhaps we should; at least until we find systems in the
> field that break with that constraint :(

Mapping should be harmless as long as we then don't touch it? I can't 
think of any circumstances where we would.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/