From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 3/3] vmdk: Convert to bdrv_open
Date: Mon, 19 Apr 2010 09:37:20 +0200 [thread overview]
Message-ID: <4BCC0830.600@redhat.com> (raw)
In-Reply-To: <y2nfbd9d3991004170239s3e25b03fs757f71e188dca36d@mail.gmail.com>
Am 17.04.2010 11:39, schrieb Stefan Hajnoczi:
> 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.
Right, I should have removed this code in patch 2/3. I'll fix that and
send a new version.
Kevin
prev parent reply other threads:[~2010-04-19 7:38 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
2010-04-19 7:37 ` Kevin Wolf [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=4BCC0830.600@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.