From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH][RFC] Handling ':' on filenames
Date: Fri, 6 Mar 2009 18:28:30 -0300 [thread overview]
Message-ID: <20090306212830.GL5077@blackpad> (raw)
This patch fixes this issue:
$ qemu-img create -f qcow2 /tmp/a:b 1G
$ qemu-system-x86_64 -hda qcow2:/tmp/a:b
qemu: could not open disk image /tmp/a:b
$
Based on a suggestion by Daniel Berrange.
However, this is still just a workaround. The semantics of filenames
containing colon characters (and how this can be escaped, avoided,
or worked around) are not very clear.
Going further, what if we stop using "protocol:filename" strings
internally, except where the user interface or external data really
requires this format?
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
---
block.c | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/block.c b/block.c
index 7c744c7..04488d6 100644
--- a/block.c
+++ b/block.c
@@ -236,6 +236,14 @@ static BlockDriver *find_protocol(const char *filename)
is_windows_drive_prefix(filename))
return &bdrv_raw;
#endif
+
+ /* Protocol name will never start with a slash.
+ * This allows the user to specify absolute filenames
+ * containing a ":" character.
+ */
+ if (*filename == '/')
+ return &bdrv_raw;
+
p = strchr(filename, ':');
if (!p)
return &bdrv_raw;
--
1.6.1
--
Eduardo
next reply other threads:[~2009-03-06 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 21:28 Eduardo Habkost [this message]
2009-03-08 11:28 ` [Qemu-devel] [PATCH][RFC] Handling ':' on filenames Uri Lublin
2009-03-08 11:49 ` Stuart Brady
2009-03-09 14:32 ` Eduardo Habkost
2009-03-09 21:11 ` Jamie Lokier
2009-03-09 14:21 ` Eduardo Habkost
2009-03-09 14:27 ` Eduardo Habkost
2009-03-10 3:59 ` Amit Shah
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=20090306212830.GL5077@blackpad \
--to=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.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).