From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: pomonis@google.com, ahonig@google.com, jmattson@google.com,
nifi@google.com, pbonzini@redhat.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] KVM: x86: Protect kvm_lapic_reg_write() from Spectre-v1/L1TF" failed to apply to 4.4-stable tree
Date: Sun, 9 Feb 2020 14:00:17 -0500 [thread overview]
Message-ID: <20200209190017.GS3584@sasha-vm> (raw)
In-Reply-To: <158124948610483@kroah.com>
On Sun, Feb 09, 2020 at 12:58:06PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.4-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 4bf79cb089f6b1c6c632492c0271054ce52ad766 Mon Sep 17 00:00:00 2001
>From: Marios Pomonis <pomonis@google.com>
>Date: Wed, 11 Dec 2019 12:47:46 -0800
>Subject: [PATCH] KVM: x86: Protect kvm_lapic_reg_write() from Spectre-v1/L1TF
> attacks
>
>This fixes a Spectre-v1/L1TF vulnerability in kvm_lapic_reg_write().
>This function contains index computations based on the
>(attacker-controlled) MSR number.
>
>Fixes: 0105d1a52640 ("KVM: x2apic interface to lapic")
>
>Signed-off-by: Nick Finco <nifi@google.com>
>Signed-off-by: Marios Pomonis <pomonis@google.com>
>Reviewed-by: Andrew Honig <ahonig@google.com>
>Cc: stable@vger.kernel.org
>Reviewed-by: Jim Mattson <jmattson@google.com>
>Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
We didn't have 1e6e2755b635 ("KVM: x86: Misc LAPIC changes to expose
helper functions") in 4.4. I've fixed it and queued this patch for 4.4.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-02-09 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 11:58 FAILED: patch "[PATCH] KVM: x86: Protect kvm_lapic_reg_write() from Spectre-v1/L1TF" failed to apply to 4.4-stable tree gregkh
2020-02-09 19:00 ` Sasha Levin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200209190017.GS3584@sasha-vm \
--to=sashal@kernel.org \
--cc=ahonig@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jmattson@google.com \
--cc=nifi@google.com \
--cc=pbonzini@redhat.com \
--cc=pomonis@google.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.