From: annie li <annie.li@oracle.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Rebooting domu fails in nfs share exported from another domu on the same dom0
Date: Thu, 17 Jul 2014 12:56:12 -0400 [thread overview]
Message-ID: <53C8002C.2020501@oracle.com> (raw)
In-Reply-To: <53C7F088.5070005@citrix.com>
On 2014/7/17 11:49, Roger Pau Monné wrote:
> On 16/07/14 22:36, annie li wrote:
>> Hi
>>
>> I hit a problem in such scenario: vm1 is running and export nfs service,
>> dom0 mount this nfs, and vm2 is booted in this nfs location. vm1 and vm2
>> are running on the same dom0.
>>
>> When this bug happens, the data flow is: vm2 blkfront-> vm2 blkback->
>> loop -> nfs file -> nfs client -> bridge priv1 -> vm1 vif -> vm1 netback
>> -> vm1 netfront.
>>
>> In above data flow, nfs implements direct io, blkfront and blkback uses
>> grantmap. This makes page mapping works well through vm2 blkfront to vm1
>> netback. However, when netback does grant copy, the error happens in
>> this routine:
> If it's the same error I was seeing (which I think it is), the problem
> is due to trying to do a grant_copy with the PFN of a grant mapped page
> in Dom0, which Xen refuses to perform.
>
> I've never followed it up, but I think the problem should be fixed in
> Linux, so that netback realises it is trying to perform a grant_copy to
> a granted page, and use the grant ref instead of the PFN.
>
I guess the routine is similar if using grant ref. See __gnttab_copy
function,
The routine goes into __acquire_grant_for_copy for grant ref, and then
__get_paged_frame->get_page_from_gfn->get_page. get_page is where the
checking page owner fails.
Thanks
Annie
next prev parent reply other threads:[~2014-07-17 16:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 20:36 Rebooting domu fails in nfs share exported from another domu on the same dom0 annie li
2014-07-17 15:49 ` Roger Pau Monné
2014-07-17 16:56 ` annie li [this message]
2014-07-18 18:53 ` Konrad Rzeszutek Wilk
2014-07-18 19:31 ` annie li
2014-07-18 19:43 ` Konrad Rzeszutek Wilk
2014-07-18 20:17 ` annie li
2014-07-18 20:22 ` Konrad Rzeszutek Wilk
2014-07-18 20:31 ` annie li
2014-07-18 21:07 ` Konrad Rzeszutek Wilk
2014-07-18 21:43 ` annie li
2014-07-21 10:02 ` Wei Liu
2014-07-21 15:02 ` annie li
2014-07-21 23:05 ` Wei Liu
2014-07-23 1:58 ` annie li
2014-07-28 14:14 ` David Vrabel
2014-07-28 16:14 ` annie li
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=53C8002C.2020501@oracle.com \
--to=annie.li@oracle.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).