From: Jeff Cody <jcody@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/1] block: check full backing filename when searching protocol filenames
Date: Wed, 25 Jan 2017 13:44:35 -0500 [thread overview]
Message-ID: <20170125184435.GA1868@localhost.localdomain> (raw)
In-Reply-To: <343adad0-1e18-5777-ad73-3d6fb7be8424@redhat.com>
On Wed, Jan 25, 2017 at 07:24:48PM +0100, Max Reitz wrote:
> On 25.01.2017 18:22, Jeff Cody wrote:
> > In bdrv_find_backing_image(), if we are searching an image for a backing
> > file that contains a protocol, we currently only compare unmodified
> > paths.
> >
> > However, some management software will change the backing filename to be
> > a relative filename in a path. QEMU is able to handle this fine,
> > because internally it will use path_combine to put together the full
> > protocol URI.
> >
> > However, this can lead to an inability to match an image during a QAPI
> > command that needs to use bdrv_find_backing_image() to find the image,
> > when it is searched by the full URI.
> >
> > When searching for a protocol filename, if the straight comparison
> > fails, this patch will also compare against the full backing filename to
> > see if that is a match.
> >
> > Signed-off-by: Jeff Cody <jcody@redhat.com>
> > ---
> > block.c | 12 ++++++++++++
> > 1 file changed, 12 insertions(+)
>
> Thanks, applied to my block tree:
>
> https://github.com/XanClic/qemu/commits/block
>
Thanks!
>
> How much would you mind writing an iotest?
I don't mind, I can do that.
-Jeff
next prev parent reply other threads:[~2017-01-25 18:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 17:22 [Qemu-devel] [PATCH 1/1] block: check full backing filename when searching protocol filenames Jeff Cody
2017-01-25 17:43 ` Jeff Cody
2017-01-25 18:24 ` Eric Blake
2017-01-25 18:25 ` Max Reitz
2017-01-25 18:24 ` Max Reitz
2017-01-25 18:44 ` Jeff Cody [this message]
2017-01-25 18:27 ` Max Reitz
2017-01-25 18:48 ` Jeff Cody
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=20170125184435.GA1868@localhost.localdomain \
--to=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).