From: David Hildenbrand <david@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cohuck@redhat.com>
Cc: KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
Thomas Huth <thuth@redhat.com>,
Halil Pasic <pasic@linux.vnet.ibm.com>,
Janosch Frank <frankja@linux.vnet.ibm.com>,
Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/1] KVM: s390: fix cmma migration for multiple memory slots
Date: Tue, 19 Dec 2017 18:11:10 +0100 [thread overview]
Message-ID: <1ac27d73-d4a7-b596-266b-8a3ff8aa6f41@redhat.com> (raw)
In-Reply-To: <20171219081921.81670-2-borntraeger@de.ibm.com>
On 19.12.2017 09:19, Christian Borntraeger wrote:
> when multiple memory slots are present the cmma migration code
> does not allocate enough memory for the bitmap. The memory slots
> are sorted in reverse order, so we must use gfn and size of
> slot[0] instead of the last one.
>
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> Reviewed-by: Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>
> Cc: stable@vger.kernel.org # 4.13+
> Fixes: 190df4a212a7 (KVM: s390: CMMA tracking, ESSA emulation, migration mode)
> ---
> arch/s390/kvm/kvm-s390.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
> index 966ea611210a..3373d8dff131 100644
> --- a/arch/s390/kvm/kvm-s390.c
> +++ b/arch/s390/kvm/kvm-s390.c
> @@ -792,11 +792,12 @@ static int kvm_s390_vm_start_migration(struct kvm *kvm)
>
> if (kvm->arch.use_cmma) {
> /*
> - * Get the last slot. They should be sorted by base_gfn, so the
> - * last slot is also the one at the end of the address space.
> - * We have verified above that at least one slot is present.
> + * Get the first slot. They are reverse sorted by base_gfn, so
> + * the first slot is also the one at the end of the address
> + * space. We have verified above that at least one slot is
> + * present.
> */
> - ms = slots->memslots + slots->used_slots - 1;
> + ms = slots->memslots;
> /* round up so we only use full longs */
> ram_pages = roundup(ms->base_gfn + ms->npages, BITS_PER_LONG);
> /* allocate enough bytes to store all the bits */
>
If I am not wrong, can't user space:
a) Create a VM, boot linux
b) Trigger VM START migration, initializing the bitmap
c) add a new memslot
c) make the guest execute an ESSA instruction on that new memslot
in do_essa(), gfn_to_hva() will now succeed and we will write into some
random memory as the bitmap is too short:
"test_and_set_bit(gfn, ms->pgste_bitmap)"
The same could be possible if the guest onlines memory (creating the
memslot via SCLP) during VM migration.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2017-12-19 17:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 8:19 [PATCH 0/1] KVM: s390: fix for 4.15 and stable Christian Borntraeger
2017-12-19 8:19 ` [PATCH 1/1] KVM: s390: fix cmma migration for multiple memory slots Christian Borntraeger
2017-12-19 10:41 ` Cornelia Huck
2017-12-19 11:04 ` Christian Borntraeger
2017-12-19 17:11 ` David Hildenbrand [this message]
2017-12-19 20:21 ` Christian Borntraeger
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=1ac27d73-d4a7-b596-266b-8a3ff8aa6f41@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@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=pasic@linux.vnet.ibm.com \
--cc=thuth@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