mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: 20220420013732.3308816-4-seanjc@google.com, kangel@zju.edu.cn,
	mlevitsk@redhat.com, pbonzini@redhat.com, pgn@zju.edu.cn,
	seanjc@google.com, stable-commits@vger.kernel.org
Subject: Re: Patch "KVM: x86: Pend KVM_REQ_APICV_UPDATE during vCPU creation to fix a race" has been added to the 5.10-stable tree
Date: Mon, 25 Apr 2022 13:45:12 +0200	[thread overview]
Message-ID: <YmaJyGgxzfx+MbgY@kroah.com> (raw)
In-Reply-To: <165088643415117@kroah.com>

On Mon, Apr 25, 2022 at 01:33:54PM +0200, gregkh@linuxfoundation.org wrote:
> 
> This is a note to let you know that I've just added the patch titled
> 
>     KVM: x86: Pend KVM_REQ_APICV_UPDATE during vCPU creation to fix a race
> 
> to the 5.10-stable tree which can be found at:
>     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> 
> The filename of the patch is:
>      kvm-x86-pend-kvm_req_apicv_update-during-vcpu-creation-to-fix-a-race.patch
> and it can be found in the queue-5.10 subdirectory.
> 
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
> 
> 
> >From 423ecfea77dda83823c71b0fad1c2ddb2af1e5fc Mon Sep 17 00:00:00 2001
> From: Sean Christopherson <seanjc@google.com>
> Date: Wed, 20 Apr 2022 01:37:31 +0000
> Subject: KVM: x86: Pend KVM_REQ_APICV_UPDATE during vCPU creation to fix a race
> 
> From: Sean Christopherson <seanjc@google.com>
> 
> commit 423ecfea77dda83823c71b0fad1c2ddb2af1e5fc upstream.

Oops, no, this breaks the build, now dropped.

           reply	other threads:[~2022-04-25 11:45 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <165088643415117@kroah.com>]

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=YmaJyGgxzfx+MbgY@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=20220420013732.3308816-4-seanjc@google.com \
    --cc=kangel@zju.edu.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlevitsk@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=pgn@zju.edu.cn \
    --cc=seanjc@google.com \
    --cc=stable-commits@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®