xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "greg@enjellic.com" <greg@enjellic.com>
Cc: "Dr. Greg Wettstein" <greg@wind.enjellic.com>,
	"scst-devel@lists.sourceforge.net"
	<scst-devel@lists.sourceforge.net>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: iSCSI connection corrupts Xen block devices.
Date: Tue, 26 Mar 2013 10:14:56 +0100	[thread overview]
Message-ID: <51516710.8000906@citrix.com> (raw)
In-Reply-To: <201303260626.r2Q6QOxM011091@wind.enjellic.com>

On 26/03/13 07:26, Dr. Greg Wettstein wrote:
> Hi, hope the week has started out well for everyone.
> 
> This report may be in the FWIW department since there may be a
> fundamental reason why this doesn't work.  We elected to report this
> to the Xen community since we thought any behavior which corrupted
> disk images needed to at least be reported.

Hello Greg,

I've also noticed this some time ago, the cause of this bug is that we
pass granted pages to netback, and when trying to perform the grant copy
operation it fails. I've sent a clumsy patch that solved the problem,
but it involves additional memcpy in order to avoid passing the granted
page to netback:

http://lists.xen.org/archives/html/xen-devel/2013-01/msg00717.html

The best solution I can think of is storing the grant frame reference
somewhere in the p2m table, and then using that reference instead of the
mfn when performing the grant copy operation.

Regards, Roger.

  reply	other threads:[~2013-03-26  9:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26  6:26 iSCSI connection corrupts Xen block devices Dr. Greg Wettstein
2013-03-26  9:14 ` Roger Pau Monné [this message]
2013-03-26 13:13 ` Konrad Rzeszutek Wilk
  -- strict thread matches above, loose matches on Subject: below --
2013-03-28  6:23 Dr. Greg Wettstein

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=51516710.8000906@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=greg@enjellic.com \
    --cc=greg@wind.enjellic.com \
    --cc=scst-devel@lists.sourceforge.net \
    --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).