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
..
kvm	KVM: set_memory_region: Disallow changing read-only attribute later	2013-02-04 22:56:47 -02:00
uml	typo in UserModeLinux-HOWTO	2012-10-09 22:35:24 +02:00
00-INDEX	lguest: remove reference from Documentation/virtual/00-INDEX	2012-01-28 08:10:23 +10:30
virtio-spec.txt	virtio: update documentation to v0.9.5 of spec	2012-05-22 12:16:09 +09:30