All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vegard Nossum <vegard.nossum@oracle.com>
To: gregkh@linuxfoundation.org, pbonzini@redhat.com, kangel@zju.edu.cn
Cc: stable@vger.kernel.org, Sean Christopherson <seanjc@google.com>
Subject: Re: FAILED: patch "[PATCH] KVM: x86/mmu: fix NULL pointer dereference on guest INVPCID" failed to apply to 5.4-stable tree
Date: Tue, 24 May 2022 22:40:31 +0200	[thread overview]
Message-ID: <67e1a766-f828-e867-096b-4dba623ca67b@oracle.com> (raw)
In-Reply-To: <165314154010137@kroah.com>

On 5/21/22 15:59, gregkh@linuxfoundation.org wrote:
> 
> The patch below does not apply to the 5.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 9f46c187e2e680ecd9de7983e4d081c3391acc76 Mon Sep 17 00:00:00 2001
> From: Paolo Bonzini <pbonzini@redhat.com>
> Date: Fri, 20 May 2022 13:48:11 -0400
> Subject: [PATCH] KVM: x86/mmu: fix NULL pointer dereference on guest INVPCID
> 

I don't think 5.4 or earlier need this patch as (AFAICT) the bug was
introduced by:

commit 5efac0741ce238e0844d3f7af00198f81e84926a
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Mon Mar 23 20:42:57 2020 -0400

    KVM: x86: introduce kvm_mmu_invalidate_gva

which was merged in v5.8 and has not been backported to v5.4.y or any
earlier stable branch.

The reproducer does not crash on latest v5.4.y, which agrees with the above.


Vegard

      reply	other threads:[~2022-05-24 20:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21 13:59 FAILED: patch "[PATCH] KVM: x86/mmu: fix NULL pointer dereference on guest INVPCID" failed to apply to 5.4-stable tree gregkh
2022-05-24 20:40 ` Vegard Nossum [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=67e1a766-f828-e867-096b-4dba623ca67b@oracle.com \
    --to=vegard.nossum@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kangel@zju.edu.cn \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@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.