linux-kernel - Re: [PATCH 7/7] x86/pci: don't check mmconf again if it is from MSR with amd faml0h

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] [day] [month] [year] [list]

Date:	Fri, 15 Jan 2010 13:16:43 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
CC:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: Re: [PATCH 7/7] x86/pci: don't check mmconf again if it is from MSR
 with amd faml0h

On 01/15/2010 11:42 AM, Jesse Barnes wrote:
> On Fri, 18 Dec 2009 12:09:58 -0800
> Yinghai Lu <yinghai@...nel.org> wrote:
> 
>>
>> for AMD Fam10h, it we read mmconf from MSR early, we should just
>> trust it because we check it and correct it already.
>>
>> so skip the reject check there.
>>
>> Signed-off-by: Yinghai Lu <yinghai@...nel.org>
> 
> My previous question wasn't answered.  Either reject_broken should be a
> no-op on this platform, or it's getting things wrong and should be
> fixed.  Adding a whitelist here seems like the wrong thing to do...
> 

let me find other way, may update e820 directly.

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