Takuya Yoshikawa 75d61fbcf5 KVM: set_memory_region: Disallow changing read-only attribute later ... As Xiao pointed out, there are a few problems with it: - kvm_arch_commit_memory_region() write protects the memory slot only for GET_DIRTY_LOG when modifying the flags. - FNAME(sync_page) uses the old spte value to set a new one without checking KVM_MEM_READONLY flag. Since we flush all shadow pages when creating a new slot, the simplest fix is to disallow such problematic flag changes: this is safe because no one is doing such things. Reviewed-by: Gleb Natapov <gleb@redhat.com> Signed-off-by: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp> Cc: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com> Cc: Alex Williamson <alex.williamson@redhat.com> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>		2013-02-04 22:56:47 -02:00
..
api.txt	KVM: set_memory_region: Disallow changing read-only attribute later	2013-02-04 22:56:47 -02:00
cpuid.txt	KVM: fix cpuid eax for KVM leaf	2012-05-06 15:51:56 +03:00
hypercalls.txt	KVM: Add documentation on hypercalls	2012-08-13 17:39:59 -03:00
locking.txt	KVM: MMU: document mmu-lock and fast page fault	2012-07-11 16:51:23 +03:00
mmu.txt	KVM: Remove unused slot_bitmap from kvm_mmu_page	2013-01-14 11:13:58 +02:00
msr.txt	KVM: clarify kvmclock documentation	2012-09-17 14:10:23 -03:00
nested-vmx.txt	KVM: nVMX: Documentation	2011-07-12 13:15:22 +03:00
ppc-pv.txt	KVM: Add ppc hypercall documentation	2012-08-13 17:39:59 -03:00
review-checklist.txt
timekeeping.txt