From: Roger Pau Monne <roger.pau@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Christoph Egger <Christoph.Egger@amd.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v3] hotplug/NetBSD: check type of file to attach from params
Date: Tue, 14 Aug 2012 16:23:57 +0100 [thread overview]
Message-ID: <502A6D8D.1030309@citrix.com> (raw)
In-Reply-To: <1344957010.5926.103.camel@zakaz.uk.xensource.com>
Ian Campbell wrote:
> On Tue, 2012-08-14 at 16:06 +0100, Roger Pau Monne wrote:
>> xend used to set the xenbus backend entry "type" to either "phy" or
>> "file", but now libxl sets it to "phy" for both file and block device.
>> We have to manually check for the type of the "param" field in order
>> to detect if we are trying to attach a file or a block device.
>>
>> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
>> Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
>> Signed-off-by: Roger Pau Monne <roger.pau@citrix.com>
>> ---
>> Changes since v2:
>>
>> * Better error messages.
>>
>> * Check if params is empty.
>>
>> * Replace xenstore_write with xenstore-write in error function.
>>
>> * Add quotation marks to xparams when testing.
>>
>> Changes since v1:
>>
>> * Check that file is either a block special file or a regular file
>> and report error otherwise.
>> ---
>> tools/hotplug/NetBSD/block | 13 +++++++++++--
>> 1 files changed, 11 insertions(+), 2 deletions(-)
>>
>> diff --git a/tools/hotplug/NetBSD/block b/tools/hotplug/NetBSD/block
>> index cf5ff3a..5ffc334 100644
>> --- a/tools/hotplug/NetBSD/block
>> +++ b/tools/hotplug/NetBSD/block
>> @@ -12,15 +12,24 @@ export PATH
>>
>> error() {
>> echo "$@" >&2
>> - xenstore_write $xpath/hotplug-status error
>> + xenstore-write $xpath/hotplug-status error
>> exit 1
>> }
>>
>>
>> xpath=$1
>> xstatus=$2
>> -xtype=$(xenstore-read "$xpath/type")
>> xparams=$(xenstore-read "$xpath/params")
>> +if [ -b "$xparams" ]; then
>> + xtype="phy"
>> +elif [ -f "$xparams" ]; then
>> + xtype="file"
>> +elif [ -z "$xparams" ]; then
>> + error "No image or block device found in $xpath/params"
>> +else
>> + error "Invalid file type for block device." \
>> + "Only block and regular image files accepted."
>
> Perhaps include $xparams in here somewhere? Perhaps $xpath too?
Thanks for the review.
I think including $xparams should be enough (since it is not null).
prev parent reply other threads:[~2012-08-14 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 15:06 [PATCH v3] hotplug/NetBSD: check type of file to attach from params Roger Pau Monne
2012-08-14 15:10 ` Ian Campbell
2012-08-14 15:23 ` Roger Pau Monne [this message]
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=502A6D8D.1030309@citrix.com \
--to=roger.pau@citrix.com \
--cc=Christoph.Egger@amd.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.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.