linux-kernel - Re: [tip:x86/urgent] x86, AMD: Disable wrongly set X86_FEATURE_LAHF

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:	Mon, 24 Aug 2009 23:44:30 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Borislav Petkov <petkovbb@...glemail.com>,
	Ingo Molnar <mingo@...e.hu>, mingo@...hat.com,
	linux-kernel@...r.kernel.org, kjwinchester@...il.com,
	tglx@...utronix.de, borislav.petkov@....com,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/urgent] x86, AMD: Disable wrongly set X86_FEATURE_LAHF_LM
 CPUID bit

On 08/24/2009 10:52 PM, Borislav Petkov wrote:
> On Mon, Aug 24, 2009 at 01:34:07PM -0700, H. Peter Anvin wrote:
>> Looks reasonable... although part of me wonders if having a pointer to
>> an array containing the entire register file in and out is even better,
>> of if I'm just overengineering at this point.
> 
> Hmm, let's have necessity determine that. I can only think of %edi being
> used as an input reg to rd/wrmsr beside %ecx but it could be very well
> that some other x86 hardware uses other regs too. Do we actually need
> all regs or a two should suffice?
> 

Hard to know.  In theory we shouldn't need ESI and EDI either!

As I said, I wouldn't have worried about it at all if it wasn't for
paravirt_ops turning these things into ABIs.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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