All of lore.kernel.org
 help / color / mirror / Atom feed
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: Refactor picdev_write() to prevent Spectre-v1/L1TF" failed to apply to 4.4-stable tree
Date: Sun, 9 Feb 2020 13:42:18 -0500	[thread overview]
Message-ID: <20200209184218.GQ3584@sasha-vm> (raw)
In-Reply-To: <158124926134148@kroah.com>

On Sun, Feb 09, 2020 at 12:54:21PM +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 14e32321f3606e4b0970200b6e5e47ee6f1e6410 Mon Sep 17 00:00:00 2001
>From: Marios Pomonis <pomonis@google.com>
>Date: Wed, 11 Dec 2019 12:47:43 -0800
>Subject: [PATCH] KVM: x86: Refactor picdev_write() to prevent Spectre-v1/L1TF
> attacks
>
>This fixes a Spectre-v1/L1TF vulnerability in picdev_write().
>It replaces index computations based on the (attacked-controlled) port
>number with constants through a minor refactoring.
>
>Fixes: 85f455f7ddbe ("KVM: Add support for in-kernel PIC emulation")
>
>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>

I took in 9fecaa9e32ae ("KVM: x86: drop picdev_in_range()") as a
dependency and queued both for 4.4.

-- 
Thanks,
Sasha

      reply	other threads:[~2020-02-09 18:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-09 11:54 FAILED: patch "[PATCH] KVM: x86: Refactor picdev_write() to prevent Spectre-v1/L1TF" failed to apply to 4.4-stable tree gregkh
2020-02-09 18:42 ` 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=20200209184218.GQ3584@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.