linux-kernel - Re: [PATCH RFC] function probe_roms accessing improper addresses

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]

Message-ID: <20121019153015.GD28212@srcf.ucam.org>
Date:	Fri, 19 Oct 2012 16:30:15 +0100
From:	Matthew Garrett <mjg@...hat.com>
To:	Randy Wright <rwright@...com>
Cc:	linux-kernel@...r.kernel.org,
	Thavatchai Makphaibulchoke <tmac@...com>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH RFC] function probe_roms accessing improper addresses

I don't think DMI checking is going to work, since (a) as you say, 
there's a risk that the ID will inadvertantly change over the lifecycle 
of the machine, and (b) there may be other machines. So if it's not 
possible to handle this by catching the MCE, I think we have two 
options:

1) Declare that any x86 hardware supported by Linux *must* support 
probing in this address region

2) Don't call probe_roms() by default, but leave it up to the graphics 
drivers. If they can get the rom by any other means then don't call it.

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