From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/2] KVM: SVM: avoid infinite loop on NPF from bad address
Date: Tue, 21 Apr 2020 19:56:21 +0000 [thread overview]
Message-ID: <20200421195621.E9E3820774@mail.kernel.org> (raw)
In-Reply-To: <20200417163843.71624-2-pbonzini@redhat.com>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 05d5a4863525 ("KVM: SVM: Workaround errata#1096 (insn_len maybe zero on SMAP violation)").
The bot has tested the following trees: v5.6.5, v5.5.18, v5.4.33.
v5.6.5: Build OK!
v5.5.18: Failed to apply! Possible dependencies:
Unable to calculate
v5.4.33: Failed to apply! Possible dependencies:
Unable to calculate
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-04-21 19:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 16:38 [PATCH 0/2] KVM: fix set_memory_region_test on AMD Paolo Bonzini
2020-04-17 16:38 ` [PATCH 1/2] KVM: SVM: avoid infinite loop on NPF from bad address Paolo Bonzini
2020-04-21 19:56 ` Sasha Levin [this message]
2020-07-08 8:17 ` Wanpeng Li
2020-07-08 8:38 ` Paolo Bonzini
2020-07-08 9:08 ` Wanpeng Li
2020-07-08 11:10 ` Paolo Bonzini
2021-06-08 4:39 ` Salvatore Bonaccorso
2021-06-08 7:17 ` Paolo Bonzini
2022-01-13 16:27 ` Query about calling kvm_vcpu_gfn_to_memslot() with a GVA (Re: " Liam Merwick
2022-01-13 16:57 ` Sean Christopherson
2022-01-17 17:09 ` Liam Merwick
2022-01-18 18:46 ` Sean Christopherson
2020-04-17 16:38 ` [PATCH 2/2] selftests: kvm/set_memory_region_test: do not check RIP if the guest shuts down Paolo Bonzini
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=20200421195621.E9E3820774@mail.kernel.org \
--to=sashal@kernel.org \
--cc=sean.j.christopherson@intel.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 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).