qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 2/4] block: in commit, determine base image from the top image
Date: Tue, 16 Oct 2012 11:31:42 -0400	[thread overview]
Message-ID: <507D7DDE.5010802@redhat.com> (raw)
In-Reply-To: <507D7BB3.7090505@redhat.com>

On 10/16/2012 11:22 AM, Eric Blake wrote:
> On 10/16/2012 08:44 AM, Jeff Cody wrote:
>> This simplifies some code and error checking, and also fixes a bug.
>>
>> bdrv_find_backing_image() should only be passed absolute filenames,
>> or filenames relative to the chain.  In the QMP message handler for
>> block commit, when looking up the base do so from the determined top
>> image, so we know it is reachable from top.
>>
>> Signed-off-by: Jeff Cody <jcody@redhat.com>
>> ---
>>  block/commit.c |  9 ---------
>>  blockdev.c     | 21 +++++++++++----------
>>  2 files changed, 11 insertions(+), 19 deletions(-)
> 
> As long as you are touching this code:
> 
>> @@ -1182,6 +1172,17 @@ void qmp_block_commit(const char *device,
>>          return;
>>      }
>>  
>> +    if (base && has_base) {
> 
> please swap this to 'has_base && base' to avoid any potential of
> valgrind warnings about conditional jump based on uninitialized memory.
>

OK.

> Also, I raised another bug[1] about a bad error message regarding
> top_bs, if the user passes a different spelling than the canonical name
> of the active image.  Is that worth fixing in this series, or is it okay
> to leave it until you actually add support for committing the top image?
> 
> [1] https://lists.gnu.org/archive/html/qemu-devel/2012-10/msg02067.html
> 

Since this doesn't pose an actual issue now, I was planning on just
addressing that with the stage-2 patches, since that will likely touch
other related areas of the code anyway.  If you have major heartburn
over this, I'll change it now.

  reply	other threads:[~2012-10-16 15:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 14:44 [Qemu-devel] [PATCH v2 0/4] block-commit fixes Jeff Cody
2012-10-16 14:44 ` [Qemu-devel] [PATCH v2 1/4] block: make bdrv_find_backing_image compare canonical filenames Jeff Cody
2012-10-16 15:12   ` Eric Blake
2012-10-16 15:40     ` Jeff Cody
2012-10-16 14:44 ` [Qemu-devel] [PATCH v2 2/4] block: in commit, determine base image from the top image Jeff Cody
2012-10-16 15:22   ` Eric Blake
2012-10-16 15:31     ` Jeff Cody [this message]
2012-10-16 15:35       ` Eric Blake
2012-10-16 14:44 ` [Qemu-devel] [PATCH v2 3/4] qemu-iotests: qemu-io tests update for block-commit (040) Jeff Cody
2012-10-16 14:44 ` [Qemu-devel] [PATCH v2 4/4] qemu-iotests: add relative backing file tests " 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=507D7DDE.5010802@redhat.com \
    --to=jcody@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@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).