aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/kvm
diff options
context:
space:
mode:
authorThomas Huth <thuth@redhat.com>2019-09-04 10:51:59 +0200
committerJanosch Frank <frankja@linux.ibm.com>2019-09-04 15:38:05 +0200
commit200824f55eef409830a2d1703d6f81542620c2f0 (patch)
treeb996508dee9c50a0ac149f4eb354a0939559ff38 /tools/testing/selftests/kvm
parentKVM: selftests: Add a test for the KVM_S390_MEM_OP ioctl (diff)
downloadlinux-dev-200824f55eef409830a2d1703d6f81542620c2f0.tar.xz
linux-dev-200824f55eef409830a2d1703d6f81542620c2f0.zip
KVM: s390: Disallow invalid bits in kvm_valid_regs and kvm_dirty_regs
If unknown bits are set in kvm_valid_regs or kvm_dirty_regs, this clearly indicates that something went wrong in the KVM userspace application. The x86 variant of KVM already contains a check for bad bits, so let's do the same on s390x now, too. Reviewed-by: Janosch Frank <frankja@linux.ibm.com> Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com> Reviewed-by: Cornelia Huck <cohuck@redhat.com> Reviewed-by: David Hildenbrand <david@redhat.com> Signed-off-by: Thomas Huth <thuth@redhat.com> Link: https://lore.kernel.org/lkml/20190904085200.29021-2-thuth@redhat.com/ Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Diffstat (limited to 'tools/testing/selftests/kvm')
0 files changed, 0 insertions, 0 deletions