Paolo Bonzini 09d952c971 KVM: check userspace_addr for all memslots ... The userspace_addr alignment and range checks are not performed for private memory slots that are prepared by KVM itself. This is unnecessary and makes it questionable to use __*_user functions to access memory later on. We also rely on the userspace address being aligned since we have an entire family of functions to map gfn to pfn. Fortunately skipping the check is completely unnecessary. Only x86 uses private memslots and their userspace_addr is obtained from vm_mmap, therefore it must be below PAGE_OFFSET. In fact, any attempt to pass an address above PAGE_OFFSET would have failed because such an address would return true for kvm_is_error_hva. Reported-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2020-06-01 04:26:14 -04:00
..
kvm	KVM: check userspace_addr for all memslots	2020-06-01 04:26:14 -04:00
lib	KVM: lib: use jump label to handle resource release in irq_bypass_register_producer()	2020-01-08 18:16:01 +01:00
Makefile	treewide: Add SPDX license identifier - Makefile/Kconfig	2019-05-21 10:50:46 +02:00