From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: linmiaohe@huawei.com, liran.alon@oracle.com, pbonzini@redhat.com,
sean.j.christopherson@intel.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] KVM: nVMX: vmread should not set rflags to specify success in" failed to apply to 5.4-stable tree
Date: Sun, 9 Feb 2020 15:32:40 -0500 [thread overview]
Message-ID: <20200209203240.GC3584@sasha-vm> (raw)
In-Reply-To: <158125178414544@kroah.com>
On Sun, Feb 09, 2020 at 01:36:24PM +0100, 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 a4d956b9390418623ae5d07933e2679c68b6f83c Mon Sep 17 00:00:00 2001
>From: Miaohe Lin <linmiaohe@huawei.com>
>Date: Sat, 28 Dec 2019 14:25:24 +0800
>Subject: [PATCH] KVM: nVMX: vmread should not set rflags to specify success in
> case of #PF
>
>In case writing to vmread destination operand result in a #PF, vmread
>should not call nested_vmx_succeed() to set rflags to specify success.
>Similar to as done in VMPTRST (See handle_vmptrst()).
>
>Reviewed-by: Liran Alon <liran.alon@oracle.com>
>Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
>Cc: stable@vger.kernel.org
>Reviewed-by: Sean Christopherson <sean.j.christopherson@intel.com>
>Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Conflict because of missing c90f4d03cce1 ("kvm: nVMX: Aesthetic cleanup
of handle_vmread and handle_vmwrite") on older kernels. Cleaned up and
queued for 5.4-4.4.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-02-09 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 12:36 FAILED: patch "[PATCH] KVM: nVMX: vmread should not set rflags to specify success in" failed to apply to 5.4-stable tree gregkh
2020-02-09 20:32 ` 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=20200209203240.GC3584@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linmiaohe@huawei.com \
--cc=liran.alon@oracle.com \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).