From: "nai.xia" <nai.xia@gmail.com>
To: Joe Epstein <jepstein98@gmail.com>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir@xen.org>,
Tim Deegan <Tim.Deegan@citrix.com>
Subject: Re: Is this a data corruption bug for p2m_ram_shared page in hvm_hap_nested_page_fault()
Date: Thu, 02 Feb 2012 18:25:43 +0800 [thread overview]
Message-ID: <4F2A64A7.9080902@gmail.com> (raw)
In-Reply-To: <4F2A62A2.1010505@gmail.com>
On 2012年02月02日 18:17, nai.xia wrote:
> 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
Oh, sorry, I notice that with p2m_ram_shared, the write permissions is always cleared.
But, still, this seems cannot lead to the call of mem_sharing_unshare_page() and this
write fault will happen again and again?
Thanks,
Nai
> , then the data in this shared page could be corrupted by this page write access?
>
>
> Thanks,
>
> Nai
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2012-02-02 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 10:17 Is this a data corruption bug for p2m_ram_shared page in hvm_hap_nested_page_fault() nai.xia
2012-02-02 10:25 ` nai.xia [this message]
2012-02-02 11:19 ` Tim Deegan
2012-02-02 11:48 ` nai.xia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F2A64A7.9080902@gmail.com \
--to=nai.xia@gmail.com \
--cc=Tim.Deegan@citrix.com \
--cc=jepstein98@gmail.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.