From: Christian Borntraeger <borntraeger@de.ibm.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Cc: KVM <kvm@vger.kernel.org>, Cornelia Huck <cohuck@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Janosch Frank <frankja@linux.vnet.ibm.com>,
David Hildenbrand <david@redhat.com>,
Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>
Subject: [GIT PULL 0/1] KVM: s390: another fix for 4.15 (via kvm/master)
Date: Wed, 24 Jan 2018 15:49:43 +0100 [thread overview]
Message-ID: <20180124144944.42930-1-borntraeger@de.ibm.com> (raw)
Paolo, Radim,
one last fix for 4.15. (if it is too late for 4.15 I can send it
for the next merge window together with the other pending patches, let
me know).
The following changes since commit c2cf265d860882b51a200e4a7553c17827f2b730:
KVM: s390: prevent buffer overrun on memory hotplug during migration (2017-12-22 15:22:41 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-master-4.15-3
for you to fetch changes up to 1de1ea7efeb9e8543212210e34518b4049ccd285:
KVM: s390: add proper locking for CMMA migration bitmap (2018-01-24 15:22:51 +0100)
----------------------------------------------------------------
KVM: s390: another fix for cmma migration
This fixes races and potential use after free in the
cmma migration code.
----------------------------------------------------------------
Christian Borntraeger (1):
KVM: s390: add proper locking for CMMA migration bitmap
arch/s390/kvm/kvm-s390.c | 18 +++++++++++-------
1 file changed, 11 insertions(+), 7 deletions(-)
next reply other threads:[~2018-01-24 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 14:49 Christian Borntraeger [this message]
2018-01-24 14:49 ` [GIT PULL 1/1] KVM: s390: add proper locking for CMMA migration bitmap Christian Borntraeger
2018-01-25 14:22 ` [GIT PULL 0/1] KVM: s390: another fix for 4.15 (via kvm/master) 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=20180124144944.42930-1-borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=imbrenda@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@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