From: Kamala Narasimhan <kamala.narasimhan@gmail.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Gianni Tedesco <gianni.tedesco@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH] xl: Perform minimal validation of virtual disk file while parsing config file
Date: Wed, 26 Jan 2011 13:02:05 -0500 [thread overview]
Message-ID: <4D40619D.40806@gmail.com> (raw)
In-Reply-To: <19776.2283.897281.370509@mariner.uk.xensource.com>
Here is a patch that special cases tap/aio during validation.
I am not taking into account qcow and qcow2 as I hear they are broken with tap and shouldn't be used for that reason.
Signed-off-by: Kamala Narasimhan <kamala.narasimhan@citrix.com>
Kamala
diff -r 67d5b8004947 tools/libxl/libxl.c
--- a/tools/libxl/libxl.c Wed Jan 26 11:58:45 2011 +0000
+++ b/tools/libxl/libxl.c Wed Jan 26 12:07:54 2011 -0500
@@ -836,22 +836,26 @@ static int validate_virtual_disk(libxl_c
static int validate_virtual_disk(libxl_ctx *ctx, char *file_name, libxl_disk_phystype disk_type)
{
struct stat stat_buf;
+ int count = 0;
if ( (file_name[0] == '\0') && (disk_type == PHYSTYPE_EMPTY) )
return 0;
- if ( stat(file_name, &stat_buf) != 0 ) {
- LIBXL__LOG_ERRNO(ctx, LIBXL__LOG_ERROR, "failed to stat %s", file_name);
+ if ( disk_type == PHYSTYPE_AIO )
+ count = strlen("vhd:");
+
+ if ( stat(&file_name[count], &stat_buf) != 0 ) {
+ LIBXL__LOG_ERRNO(ctx, LIBXL__LOG_ERROR, "failed to stat %s", &file_name[count]);
return ERROR_INVAL;
}
if ( disk_type == PHYSTYPE_PHY ) {
if ( !(S_ISBLK(stat_buf.st_mode)) ) {
LIBXL__LOG(ctx, LIBXL__LOG_ERROR, "Virtual disk %s is not a block device!\n",
- file_name);
+ &file_name[count]);
return ERROR_INVAL;
}
} else if ( S_ISREG(stat_buf.st_mode) && stat_buf.st_size == 0 ) {
- LIBXL__LOG(ctx, LIBXL__LOG_ERROR, "Virtual disk %s size is 0!\n", file_name);
+ LIBXL__LOG(ctx, LIBXL__LOG_ERROR, "Virtual disk %s size is 0!\n", &file_name[count]);
return ERROR_INVAL;
}
next prev parent reply other threads:[~2011-01-26 18:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 15:35 [PATCH] xl: Perform minimal validation of virtual disk file while parsing config file Kamala Narasimhan
2011-01-14 9:05 ` Ian Campbell
2011-01-14 14:55 ` Kamala Narasimhan
2011-01-14 16:59 ` Gianni Tedesco
2011-01-14 17:17 ` Kamala Narasimhan
2011-01-19 18:09 ` Kamala Narasimhan
2011-01-19 18:26 ` Kamala Narasimhan
2011-01-20 14:04 ` Gianni Tedesco
2011-01-20 14:12 ` Gianni Tedesco
2011-01-20 15:08 ` Kamala Narasimhan
2011-01-20 15:22 ` Gianni Tedesco
2011-01-20 15:22 ` Kamala Narasimhan
2011-01-20 15:41 ` Kamala Narasimhan
2011-01-20 15:49 ` Ian Jackson
2011-01-20 16:46 ` Kamala Narasimhan
2011-01-20 21:14 ` Kamala Narasimhan
2011-01-21 12:17 ` Ian Jackson
2011-01-21 13:27 ` Gianni Tedesco
2011-01-22 2:33 ` Kamala Narasimhan
2011-01-25 18:10 ` Ian Jackson
2011-01-26 3:07 ` Kamala Narasimhan
2011-01-26 11:43 ` Ian Jackson
2011-01-26 18:02 ` Kamala Narasimhan [this message]
2011-01-26 10:27 ` Ian Campbell
2011-01-26 11:48 ` Ian Jackson
2011-01-26 11:54 ` Ian Campbell
2011-01-24 14:18 ` Kamala Narasimhan
2011-01-24 14:31 ` Kamala Narasimhan
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=4D40619D.40806@gmail.com \
--to=kamala.narasimhan@gmail.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=gianni.tedesco@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).