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:48:45 -0500 [thread overview]
Message-ID: <20170125184845.GB1868@localhost.localdomain> (raw)
In-Reply-To: <94c9b54b-7a6b-a6db-3866-d96311920a33@redhat.com>
On Wed, Jan 25, 2017 at 07:27:07PM +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(+)
> >
> > diff --git a/block.c b/block.c
> > index 39ddea3..a173afc 100644
> > --- a/block.c
> > +++ b/block.c
> > @@ -3145,6 +3145,7 @@ BlockDriverState *bdrv_find_backing_image(BlockDriverState *bs,
> > int is_protocol = 0;
> > BlockDriverState *curr_bs = NULL;
> > BlockDriverState *retval = NULL;
> > + Error *local_error = NULL;
> >
> > if (!bs || !bs->drv || !backing_file) {
> > return NULL;
> > @@ -3165,6 +3166,17 @@ BlockDriverState *bdrv_find_backing_image(BlockDriverState *bs,
> > retval = curr_bs->backing->bs;
> > break;
> > }
> > + /* Also check against the full backing filename for the image */
> > + bdrv_get_full_backing_filename(curr_bs, backing_file_full, PATH_MAX,
> > + &local_error);
> > + if (local_error == NULL) {
> > + if (strcmp(backing_file, backing_file_full) == 0) {
> > + retval = curr_bs->backing->bs;
> > + break;
> > + }
> > + } else {
> > + error_free(local_error);
>
> Oops, I was a bit too quick there. You should either follow Eric's
> remark about the scope, or you have to reset local_error to NULL here.
>
OK. I'll submit a v2, and add an iotest to that as well.
>
> > + }
> > } else {
> > /* If not an absolute filename path, make it relative to the current
> > * image's filename path */
> >
>
>
prev parent reply other threads:[~2017-01-25 18:48 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
2017-01-25 18:27 ` Max Reitz
2017-01-25 18:48 ` Jeff Cody [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=20170125184845.GB1868@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).