From mboxrd@z Thu Jan 1 00:00:00 1970 From: "nai.xia" Subject: Is this a data corruption bug for p2m_ram_shared page in hvm_hap_nested_page_fault() Date: Thu, 02 Feb 2012 18:17:06 +0800 Message-ID: <4F2A62A2.1010505@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Joe Epstein Cc: xen-devel@lists.xensource.com, Keir Fraser , Tim Deegan List-Id: xen-devel@lists.xenproject.org Hi, In hvm_hap_nested_page_fault(), it seems that all valid write faults are now handled by p2m_mem_access_check(), right? Then when will mem_sharing_unshare_page() be called? And if p2m->access_required == false, the access restrictions is cleared , then the data in this shared page could be corrupted by this page write access? Thanks, Nai