From: Ian Campbell <ian.campbell@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Ian Jackson <ian.jackson@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v2] libxl: Make local_initiate_attach more rational
Date: Fri, 3 Jul 2015 15:28:12 +0100 [thread overview]
Message-ID: <1435933692.9447.133.camel@citrix.com> (raw)
In-Reply-To: <55957AFD.6020903@citrix.com>
On Thu, 2015-07-02 at 19:55 +0200, Roger Pau Monné wrote:
> El 02/07/15 a les 19.42, George Dunlap ha escrit:
> > There are a lot of paths through
> > libxl__device_disk_local_initiate_attach(), but they all really boil
> > down to one thing: Can we just access the file directly, or do we need
> > to attach it?
> >
> > The requirements for direct access are fairly simple:
> > * Is this local (as opposed to a driver domain)?
> > * Is this a raw format (as opposed to cooked)?
> > * Does this have no scripts associated with it?
> >
> > If it meets all those requirements, we can access it directly;
> > otherwise we need to attach it.
> >
> > This fixes a bug where bootloader execution fails for disks with
> > hotplug scripts.
> >
> > This should fix a theoretical bug when using a qdisk backend in a
> > driver domain. (Not tested.)
> >
> > Based on a patch by Roger Pau Monne <roger.pau@citrix.com>.
> >
> > Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
>
> LGTM
>
> Acked-by: Roger Pau Monné <roger.pau@citrix.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-07-03 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 17:42 [PATCH v2] libxl: Make local_initiate_attach more rational George Dunlap
2015-07-02 17:55 ` Roger Pau Monné
2015-07-03 14:28 ` Ian Campbell [this message]
2015-07-06 9:44 ` George Dunlap
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=1435933692.9447.133.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@citrix.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@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 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.