From: George Dunlap <george.dunlap@eu.citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Dave Scott <Dave.Scott@eu.citrix.com>,
Sylvain Munaut <s.munaut@whatever-company.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] libxl: stat the path for all non-qdisk backends (including unknown)
Date: Fri, 26 Apr 2013 15:42:05 +0100 [thread overview]
Message-ID: <517A923D.3020806@eu.citrix.com> (raw)
In-Reply-To: <517A919F.6010406@citrix.com>
On 26/04/13 15:39, Roger Pau Monne wrote:
> On 26/04/13 16:29, Ian Campbell wrote:
>> On Fri, 2013-04-26 at 15:17 +0100, Sylvain Munaut wrote:
>>>> Since the intention of that commit was to allow for qdisk backends with no
>>>> explicit file in dom0 (i.e. network remote backend such as ceph) the lowest
>>>> impact fix appears to be to make that explicit. This should probably be
>>>> revisited to rationalize the probing.
>>> What about the remote disk case of blktap ? blktap2.5 supports NBD
>>> already AFAIK
>>> and I'm pretty sure I'll hit that same stat issue soon for another
>>> remote blktap case.
>> Right, sounds like I should have gone with my first instinct which was:
>>
>> 8<------------------------------------------------------------
>>
>> From 884beff4a897d785f61705dcfa2f048536982d7c Mon Sep 17 00:00:00 2001
>> From: Ian Campbell <ian.campbell@citrix.com>
>> Date: Fri, 26 Apr 2013 12:41:43 +0100
>> Subject: [PATCH] libxl: stat the path for all non-qdisk backends (including unknown)
>>
>> The commit a8a1f236a296 "libxl: Only call stat() when adding a disk if we
>> expect a device to exist." changed things to only stat the file when the phy
>> backend was explicitly requested. This broke the case where we are probing and
>> would normally be able to decide on the phy option.
>>
>> Since the intention of that commit was to allow for backends with no explicit
>> file in dom0 (i.e. network remote backend such as ceph) the lowest impact fix
>> appears to be to make that explicit. It turns out that tap disk can also
>> potentially handle such paths.
>>
>> The only backend which requires a local file/device is PHY but we need to
>> handle UNKNOWN too in order for subsequent probing to work. Note that it is
>> not possible to autoprobe the backend if the path is not a local object, so we
>> don't need to worry about autoprobing ceph etc.
>>
>> This should probably be revisited to rationalize the probing.
>>
>> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> Acked-by: Roger Pau Monné <roger.pau@citrix.com>
This is a fix, right? Assuming it is:
Acked-by: George Dunlap <george.dunlap@eu.citrix.com>
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-04-26 14:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 14:12 [PATCH] libxl: stat the path for all non-qdisk backends (including unknown) Ian Campbell
2013-04-26 14:17 ` Sylvain Munaut
2013-04-26 14:29 ` Ian Campbell
2013-04-26 14:39 ` Roger Pau Monné
2013-04-26 14:42 ` George Dunlap [this message]
2013-04-26 14:47 ` Ian Campbell
2013-04-26 15:33 ` Ian Campbell
2013-04-26 15:48 ` David Scott
2013-05-10 13:46 ` George Dunlap
2013-05-10 13:49 ` Ian Campbell
2013-05-10 13:55 ` George Dunlap
2013-05-10 14:09 ` Ian Campbell
2013-05-10 14:21 ` David Scott
2013-05-10 14:09 ` David Scott
2013-05-10 14:19 ` George Dunlap
2013-05-10 14:31 ` David Scott
2013-05-10 14:42 ` George Dunlap
2013-05-10 15:03 ` David Scott
2013-05-10 15:07 ` George Dunlap
2013-05-10 15:09 ` Ian Campbell
2013-04-26 14:29 ` Roger Pau Monné
2013-04-26 14:34 ` Ian Campbell
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=517A923D.3020806@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Dave.Scott@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=roger.pau@citrix.com \
--cc=s.munaut@whatever-company.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.