qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 3/3] vmdk: Convert to bdrv_open
Date: Sat, 17 Apr 2010 10:39:57 +0100	[thread overview]
Message-ID: <y2nfbd9d3991004170239s3e25b03fs757f71e188dca36d@mail.gmail.com> (raw)
In-Reply-To: <1271447998-24718-4-git-send-email-kwolf@redhat.com>

On Fri, Apr 16, 2010 at 8:59 PM, Kevin Wolf <kwolf@redhat.com> wrote:
> diff --git a/block/vmdk.c b/block/vmdk.c
> index 781518a..27b6360 100644
> --- a/block/vmdk.c
> +++ b/block/vmdk.c
> @@ -835,14 +828,12 @@ static void vmdk_close(BlockDriverState *bs)
>     qemu_free(s->l1_table);
>     qemu_free(s->l2_cache);
>     // try to close parent image, if exist
> -    vmdk_parent_close(s->hd);
> -    bdrv_delete(s->hd);
> +    vmdk_parent_close(bs->file);
>  }

block.c:bdrv_close() calls bdrv_delete(bs->backing_hd) before
bs->bdrv_close().  The vmdk format doesn't need to explicitly close
its parent file and the vmdk_parent_close() function can be deleted.
vmdk.c is the only block driver that explicitly closes or deletes
backing_hd.

Stefan

  reply	other threads:[~2010-04-17  9:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-16 19:59 [Qemu-devel] [PATCH 0/3] vmdk: Backing file fix and cleanup Kevin Wolf
2010-04-16 19:59 ` [Qemu-devel] [PATCH 1/3] vmdk: Fix COW Kevin Wolf
2010-04-17  9:08   ` Stefan Hajnoczi
2010-04-16 19:59 ` [Qemu-devel] [PATCH 2/3] vmdk: Clean up backing file handling Kevin Wolf
2010-04-17 17:38   ` Stefan Hajnoczi
2010-04-19 12:40   ` [Qemu-devel] [PATCH v2 " Kevin Wolf
2010-04-19 13:33     ` Stefan Hajnoczi
2010-04-16 19:59 ` [Qemu-devel] [PATCH 3/3] vmdk: Convert to bdrv_open Kevin Wolf
2010-04-17  9:39   ` Stefan Hajnoczi [this message]
2010-04-19  7:37     ` Kevin Wolf

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=y2nfbd9d3991004170239s3e25b03fs757f71e188dca36d@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    /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).