[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALMp9eS+8kwmTyYDieNkhbRMBW-rkphKh4fmtV3X2d9XVh3U8Q@mail.gmail.com>
Date: Mon, 6 Jan 2020 12:19:30 -0800
From: Jim Mattson <jmattson@...gle.com>
To: Marios Pomonis <pomonis@...gle.com>
Cc: Paolo Bonzini <pbonzini@...hat.com>,
Radim Krčmář <rkrcmar@...hat.com>,
Sean Christopherson <sean.j.christopherson@...el.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Joerg Roedel <joro@...tes.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>,
"the arch/x86 maintainers" <x86@...nel.org>,
kvm list <kvm@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Nick Finco <nifi@...gle.com>, Andrew Honig <ahonig@...gle.com>,
stable@...r.kernel.org
Subject: Re: [PATCH v2 12/13] KVM: x86: Protect DR-based index computations
from Spectre-v1/L1TF attacks
On Wed, Dec 11, 2019 at 12:49 PM Marios Pomonis <pomonis@...gle.com> wrote:
>
> This fixes a Spectre-v1/L1TF vulnerability in __kvm_set_dr() and
> kvm_get_dr().
> Both kvm_get_dr() and kvm_set_dr() (a wrapper of __kvm_set_dr()) are
> exported symbols so KVM should tream them conservatively from a security
> perspective.
>
> Fixes: commit 020df0794f57 ("KVM: move DR register access handling into generic code")
>
> Signed-off-by: Nick Finco <nifi@...gle.com>
> Signed-off-by: Marios Pomonis <pomonis@...gle.com>
> Reviewed-by: Andrew Honig <ahonig@...gle.com>
> Cc: stable@...r.kernel.org
Reviewed-by: Jim Mattson <jmattson@...gle.com>
Powered by blists - more mailing lists