This is a note to let you know that I've just added the patch titled
KVM: mips: use id_to_memslot correctly
to the 4.1-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
kvm-mips-use-id_to_memslot-correctly.patch
and it can be found in the queue-4.1 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From 69a1220060c1523fd0515216eaa29e22f133b894 Mon Sep 17 00:00:00 2001
From: Paolo Bonzini <[email protected]>
Date: Mon, 18 May 2015 08:35:43 +0200
Subject: KVM: mips: use id_to_memslot correctly
From: Paolo Bonzini <[email protected]>
commit 69a1220060c1523fd0515216eaa29e22f133b894 upstream.
The argument to KVM_GET_DIRTY_LOG is a memslot id; it may not match the
position in the memslots array, which is sorted by gfn.
Reviewed-by: James Hogan <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
arch/mips/kvm/mips.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/arch/mips/kvm/mips.c
+++ b/arch/mips/kvm/mips.c
@@ -982,7 +982,7 @@ int kvm_vm_ioctl_get_dirty_log(struct kv
/* If nothing is dirty, don't bother messing with page tables. */
if (is_dirty) {
- memslot = &kvm->memslots->memslots[log->slot];
+ memslot = id_to_memslot(kvm->memslots, log->slot);
ga = memslot->base_gfn << PAGE_SHIFT;
ga_end = ga + (memslot->npages << PAGE_SHIFT);
Patches currently in stable-queue which might be from [email protected] are
queue-4.1/kvm-s390-clear-floating-interrupt-bitmap-and-parameters.patch
queue-4.1/kvm-s390-virtio-ccw-don-t-overwrite-config-space-values.patch
queue-4.1/kvm-nsvm-check-for-nrips-support-before-updating-control-field.patch
queue-4.1/kvm-x86-properly-restore-lvt0.patch
queue-4.1/kvm-mips-use-id_to_memslot-correctly.patch
queue-4.1/kvm-x86-make-vapics_in_nmi_mode-atomic.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
