linux-kernel - Re: [patch V2 0/7] x86/kvm: RCU/context tracking and instrumentation protections

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: <1b17c3ed-e53c-2e20-2880-882fdc84f622@redhat.com>
Date:   Wed, 8 Jul 2020 22:28:51 +0200
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Thomas Gleixner <tglx@...utronix.de>,
        LKML <linux-kernel@...r.kernel.org>
Cc:     x86@...nel.org, kvm@...r.kernel.org,
        Alexandre Chartre <alexandre.chartre@...cle.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Juergen Gross <jgross@...e.com>
Subject: Re: [patch V2 0/7] x86/kvm: RCU/context tracking and instrumentation
 protections

On 08/07/20 21:51, Thomas Gleixner wrote:
> Folks,
> 
> this is a rebased and adopted version of the original series which is
> available here:
> 
>      https://lore.kernel.org/r/20200519203128.773151484@linutronix.de
>  
> It deals with the RCU and context tracking state and the protection against
> instrumentation in sensitive places:
> 
>   - Placing the guest_enter/exit() calls at the correct place
> 
>   - Moving the sensitive VMENTER/EXIT code into the non-instrumentable code
>     section.
> 
>   - Fixup the tracing code to comply with the non-instrumentation rules
> 
>   - Use native functions to access CR2 and the GS base MSR in the critical
>     code pathes to prevent them from being instrumented.
> 
> Thanks,
> 
> 	tglx
> 

Queued, thanks.

Paolo