diff options
| author | Julius Niedworok | 2016-08-03 16:39:55 +0200 |
|---|---|---|
| committer | Christian Borntraeger | 2016-08-12 09:11:08 +0200 |
| commit | aca411a4b17a4aebe14ecdf253373db5b7ee6058 (patch) | |
| tree | e3457792ac4e54969e665477ebbbe8c6869ed9b9 /kernel/time/timeconv.c | |
| parent | KVM: s390: set the prefix initially properly (diff) | |
| download | kernel-qcow2-linux-aca411a4b17a4aebe14ecdf253373db5b7ee6058.tar.gz kernel-qcow2-linux-aca411a4b17a4aebe14ecdf253373db5b7ee6058.tar.xz kernel-qcow2-linux-aca411a4b17a4aebe14ecdf253373db5b7ee6058.zip | |
KVM: s390: reset KVM_REQ_MMU_RELOAD if mapping the prefix failed
When triggering KVM_RUN without a user memory region being mapped
(KVM_SET_USER_MEMORY_REGION) a validity intercept occurs. This could
happen, if the user memory region was not mapped initially or if it
was unmapped after the vcpu is initialized. The function
kvm_s390_handle_requests checks for the KVM_REQ_MMU_RELOAD bit. The
check function always clears this bit. If gmap_mprotect_notify
returns an error code, the mapping failed, but the KVM_REQ_MMU_RELOAD
was not set anymore. So the next time kvm_s390_handle_requests is
called, the execution would fall trough the check for
KVM_REQ_MMU_RELOAD. The bit needs to be resetted, if
gmap_mprotect_notify returns an error code. Resetting the bit with
kvm_make_request(KVM_REQ_MMU_RELOAD, vcpu) fixes the bug.
Reviewed-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Julius Niedworok <jniedwor@linux.vnet.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Diffstat (limited to 'kernel/time/timeconv.c')
0 files changed, 0 insertions, 0 deletions