diff options
author | Christian Borntraeger | 2017-12-22 10:54:20 +0100 |
---|---|---|
committer | Christian Borntraeger | 2018-01-24 15:22:51 +0100 |
commit | 1de1ea7efeb9e8543212210e34518b4049ccd285 (patch) | |
tree | 0057ad8dc61f521d48a02caa2708e2e7a76cb6a7 /crypto/gcm.c | |
parent | c2cf265d860882b51a200e4a7553c17827f2b730 (diff) |
KVM: s390: add proper locking for CMMA migration bitmap
Some parts of the cmma migration bitmap is already protected
with the kvm->lock (e.g. the migration start). On the other
hand the read of the cmma bits is not protected against a
concurrent free, neither is the emulation of the ESSA instruction.
Let's extend the locking to all related ioctls by using
the slots lock for
- kvm_s390_vm_start_migration
- kvm_s390_vm_stop_migration
- kvm_s390_set_cmma_bits
- kvm_s390_get_cmma_bits
In addition to that, we use synchronize_srcu before freeing
the migration structure as all users hold kvm->srcu for read.
(e.g. the ESSA handler).
Reported-by: David Hildenbrand <david@redhat.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: stable@vger.kernel.org # 4.13+
Fixes: 190df4a212a7 (KVM: s390: CMMA tracking, ESSA emulation, migration mode)
Reviewed-by: Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Diffstat (limited to 'crypto/gcm.c')
0 files changed, 0 insertions, 0 deletions