linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: [GIT PULL] KVM fixes for Linux 4.15-rc7
Date: Sat, 6 Jan 2018 22:34:04 +0100	[thread overview]
Message-ID: <20180106213403.GA14958@flask> (raw)

Linus,

The following changes since commit aa12f594f97efe50223611dbd13ecca4e8dafee6:

  tools/kvm_stat: sort '-f help' output (2017-12-21 13:03:32 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/virt/kvm/kvm for-linus

for you to fetch changes up to bb4945e60dd0b5afb0e92bc8006ce560948fbc39:

  Merge tag 'kvm-s390-master-4.15-2' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux (2018-01-06 17:26:37 +0100)

----------------------------------------------------------------
KVM fixes for v4.15-rc7

s390:
* Two fixes for potential bitmap overruns in the cmma migration code

x86:
* Clear guest provided GPRs to defeat the Project Zero PoC for CVE
  2017-5715

----------------------------------------------------------------
Christian Borntraeger (2):
      KVM: s390: fix cmma migration for multiple memory slots
      KVM: s390: prevent buffer overrun on memory hotplug during migration

Jim Mattson (1):
      kvm: vmx: Scrub hardware GPRs at VM-exit

Radim Krčmář (1):
      Merge tag 'kvm-s390-master-4.15-2' of git://git.kernel.org/.../kvms390/linux

 arch/s390/kvm/kvm-s390.c |  9 +++++----
 arch/s390/kvm/priv.c     |  2 +-
 arch/x86/kvm/svm.c       | 19 +++++++++++++++++++
 arch/x86/kvm/vmx.c       | 14 +++++++++++++-
 4 files changed, 38 insertions(+), 6 deletions(-)

                 reply	other threads:[~2018-01-06 21:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180106213403.GA14958@flask \
    --to=rkrcmar@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=torvalds@linux-foundation.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).