All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
	stable <stable@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>, Jared Epp <jaredepp@pm.me>
Subject: Re: Please apply commit 6470accc7ba9 ("KVM: x86: hyper-v: Avoid calling kvm_make_vcpus_request_mask() with vcpu_mask==NULL") to v5.10.y
Date: Thu, 11 May 2023 16:47:03 -0700	[thread overview]
Message-ID: <ZF1+d2XYcQ9xvUw1@google.com> (raw)
In-Reply-To: <ZF18X3e6rrkACcMf@sashalap>

On Thu, May 11, 2023, Sasha Levin wrote:
> On Wed, May 10, 2023 at 02:57:22PM +0200, Salvatore Bonaccorso wrote:
> > Hi
> > 
> > After we updated the kernel in Debian bullseye from 5.10.162 to
> > 5.10.178, we got a report from Jared Epp in
> > https://bugs.debian.org/1035779 that a Windows Guest VM no longer
> > booted, and Kernel reporting:
> 
> This KVM commit wasn't tagged for stable, and would need an ack from the
> KVM maintainers to apply.

For grabbing commit 6470accc7ba9,

  Acked-by: Sean Christopherson <seanjc@google.com>

If it helps,

  Fixes: 6100066358ee ("KVM: Optimize kvm_make_vcpus_request_mask() a bit")

That optimization got pulled in without the undocumented dependency due to:

  Stable-dep-of: 2b0128127373 ("KVM: Register /dev/kvm as the _very_ last thing during initialization")

  reply	other threads:[~2023-05-11 23:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 12:57 Please apply commit 6470accc7ba9 ("KVM: x86: hyper-v: Avoid calling kvm_make_vcpus_request_mask() with vcpu_mask==NULL") to v5.10.y Salvatore Bonaccorso
2023-05-11 23:38 ` Sasha Levin
2023-05-11 23:47   ` Sean Christopherson [this message]
2023-05-13  9:28     ` Greg Kroah-Hartman

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=ZF1+d2XYcQ9xvUw1@google.com \
    --to=seanjc@google.com \
    --cc=carnil@debian.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jaredepp@pm.me \
    --cc=pbonzini@redhat.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vkuznets@redhat.com \
    /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.