From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/3] block: Fix backing paths for filenames with colons
Date: Fri, 26 May 2017 19:30:09 +0200 [thread overview]
Message-ID: <d3ad6b89-4666-72e3-faaa-7b80c62a99a3@redhat.com> (raw)
In-Reply-To: <20170522195217.12991-1-mreitz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
On 2017-05-22 21:52, Max Reitz wrote:
> There are (at least) two issues with filenames that contain colons when
> trying to use relative backing filenames with them, for each of which
> there is a patch in this series.
>
> The first patch fixes an issue in the general block layer
> (path_combine() does not have the same opinion on what constitutes a
> protocol prefix as path_has_protocl()), the second fixes an issue in
> file-* (when stripping off the optional "file:" prefix we should not
> create a filename that seems to have another valid protocol prefix).
>
> The third patch adds a test.
Applied to my block tree, with the spelling in patch 3 fixed as
indicated by Eric.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 498 bytes --]
prev parent reply other threads:[~2017-05-26 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 19:52 [Qemu-devel] [PATCH v2 0/3] block: Fix backing paths for filenames with colons Max Reitz
2017-05-22 19:52 ` [Qemu-devel] [PATCH v2 1/3] " Max Reitz
2017-05-22 19:52 ` [Qemu-devel] [PATCH v2 2/3] block/file-*: *_parse_filename() and colons Max Reitz
2017-05-22 20:02 ` Eric Blake
2017-05-22 19:52 ` [Qemu-devel] [PATCH v2 3/3] iotests: Add test for colon handling Max Reitz
2017-05-22 20:06 ` Eric Blake
2017-05-22 20:17 ` Max Reitz
2017-05-26 17:30 ` Max Reitz [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=d3ad6b89-4666-72e3-faaa-7b80c62a99a3@redhat.com \
--to=mreitz@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--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).