From: Paul Mackerras <paulus@ozlabs.org>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
kvm@vger.kernel.org
Cc: kvm-ppc@vger.kernel.org, David Gibson <david@gibson.dropbear.id.au>
Subject: [GIT PULL] Please pull my kvm-ppc-fixes-5.3-1 tag
Date: Tue, 27 Aug 2019 19:53:38 +1000 [thread overview]
Message-ID: <20190827095338.GA22875@blackberry> (raw)
Paolo or Radim,
Please do a pull from my kvm-ppc-fixes-5.3-1 tag to get one small
commit which I would like to go to Linus for 5.3 if possible, since it
fixes a bug where a malicious guest could cause host CPUs to hang
hard. The fix is small and obviously correct.
Thanks,
Paul.
The following changes since commit e4427372398c31f57450565de277f861a4db5b3b:
selftests/kvm: make platform_info_test pass on AMD (2019-08-21 19:08:18 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-fixes-5.3-1
for you to fetch changes up to ddfd151f3def9258397fcde7a372205a2d661903:
KVM: PPC: Book3S: Fix incorrect guest-to-user-translation error handling (2019-08-27 10:59:30 +1000)
----------------------------------------------------------------
KVM/PPC fix for 5.3
- Fix bug which could leave locks locked in the host on return
to a guest.
----------------------------------------------------------------
Alexey Kardashevskiy (1):
KVM: PPC: Book3S: Fix incorrect guest-to-user-translation error handling
arch/powerpc/kvm/book3s_64_vio.c | 6 ++++--
arch/powerpc/kvm/book3s_64_vio_hv.c | 6 ++++--
2 files changed, 8 insertions(+), 4 deletions(-)
next reply other threads:[~2019-08-27 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 9:53 Paul Mackerras [this message]
2019-08-27 15:49 ` [GIT PULL] Please pull my kvm-ppc-fixes-5.3-1 tag Radim Krčmář
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=20190827095338.GA22875@blackberry \
--to=paulus@ozlabs.org \
--cc=david@gibson.dropbear.id.au \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox