linux-kernel - Re: [PATCH v1 2/3] x86/bugs: Add AMD's SPEC

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, 4 Jun 2018 16:54:47 -0400
From:   Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:     Tom Lendacky <thomas.lendacky@....com>
Cc:     linux-kernel@...r.kernel.org, kvm@...r.kernel.org, x86@...nel.org,
        tglx@...utronix.de, andrew.cooper3@...rix.com,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>,
        Paolo Bonzini <pbonzini@...hat.com>,
        Radim Krčmář <rkrcmar@...hat.com>,
        Joerg Roedel <joro@...tes.org>, Borislav Petkov <bp@...e.de>,
        David Woodhouse <dwmw@...zon.co.uk>,
        Janakarajan Natarajan <Janakarajan.Natarajan@....com>,
        Kees Cook <keescook@...omium.org>,
        KarimAllah Ahmed <karahmed@...zon.de>,
        Andy Lutomirski <luto@...nel.org>
Subject: Re: [PATCH v1 2/3] x86/bugs: Add AMD's SPEC_CTRL MSR usage

On Mon, Jun 04, 2018 at 03:43:17PM -0500, Tom Lendacky wrote:
> On 6/4/2018 3:20 PM, Konrad Rzeszutek Wilk wrote:
> >>> diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
> >>> index 26110c202b19..950ec50f77c3 100644
> >>> --- a/arch/x86/kvm/svm.c
> >>> +++ b/arch/x86/kvm/svm.c
> >>> @@ -4115,7 +4115,8 @@ static int svm_get_msr(struct kvm_vcpu *vcpu, struct msr_data *msr_info)
> >>>  		break;
> >>>  	case MSR_IA32_SPEC_CTRL:
> >>>  		if (!msr_info->host_initiated &&
> >>> -		    !guest_cpuid_has(vcpu, X86_FEATURE_AMD_IBRS))
> >>> +		    !guest_cpuid_has(vcpu, X86_FEATURE_AMD_IBRS) &&
> >>> +		    !guest_cpuid_has(vcpu, X86_FEATURE_AMD_SSBD))
> >>
> >> Shouldn't the IBRS/SSBD check be an "or" check?  I don't think it's
> >> necessarily true that IBRS and SSBD have to both be set.  Maybe something
> >> like:
> >>
> >> 	if (!msr_info->host_initiated &&
> >> 	    !(guest_cpuid_has(vcpu, X86_FEATURE_AMD_IBRS) ||
> >> 	      guest_cpuid_has(vcpu, X86_FEATURE_AMD_SSBD))
> >>
> >> Does that make sense?
> > 
> > The '!' on each of the CPUID and '&&' make this the same. See:
> 
> Doh!  Yes, I don't know what I was thinking.  Just the end of a long
> week I guess.

<grins> I can imagine!
> 
> > 
> > 
> >  AMD_IBRS set	|  AMD_SSBD set	| !AMD_IBRS && !AMD_SSBD | !(AMD_IBRS || AMD_SSBD)
> > 	0	|	0	| 1 && 1 -> return 1	 | !(0) -> 1 -> return 1
> > 	1	|	0	| 0 && 1, continue	 | !(1 || 0) -> continue
> > 	1	|	1	| 0 && 0, continue	 | !(1 || 1) -> continue
> > 	0	|	1	| 1 && 0, continue	 | !(0 || 1) -> continue
> > 
> > Meaning we will return 1 if:
> >  the host has not initiator it or,
> >  the guest CPUID does not have AMD_IBRS flag or,
> >  the guest CPUID does not have AMD SSBD flag
> > 
> > I am fine modifying it the way you had in mind, but in the past the logic
> > was to use ! and &&, hence stuck to that.
> 
> No reason to change, it's fine the way you have it.

Excellent. Would you be OK giving it an Acked by or such?

Thanks.