From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: Max Reitz <mreitz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] block: Close backing file early in bdrv_img_create
Date: Mon, 02 Dec 2013 11:37:36 +0800 [thread overview]
Message-ID: <529C0080.7070106@linux.vnet.ibm.com> (raw)
In-Reply-To: <1385757689-23524-1-git-send-email-mreitz@redhat.com>
于 2013/11/30 4:41, Max Reitz 写道:
> Leaving the backing file open although it is not needed anymore can
> cause problems if it is opened through a block driver which allows
> exclusive access only and if the create function of the block driver
> used for the top image (the one being created) tries to close and reopen
> the image file (which will include opening the backing file a second
> time).
>
> In particular, this will happen with a backing file opened through
> qemu-nbd and using qcow2 as the top image file format (which reopens the
> image to flush it to disk).
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> v2:
> - Minimizing the changes prevents introducing a leak of the
> BlockDriverState in case of an error in bdrv_open() (thanks, Kevin).
> ---
> block.c | 3 +++
> 1 file changed, 3 insertions(+)
>
Minor comments:
I think your v1 have better orgnize of code, since it tips reader
that bs is a variable used only in backing file code. Why not improve
it by just adding one line in v1:
line 4587:
ret = bdrv_open(bs, backing_file->value.s, NULL, back_flags,
backing_drv, &local_err);
if (ret < 0) {
error_setg_errno(errp, -ret, "Could not open '%s': %s",
backing_file->value.s,
error_get_pretty(local_err));
error_free(local_err);
local_err = NULL;
bdrv_unref(bs);
goto out;
}
It is not a big problem, I am OK if you stick to this version.
next prev parent reply other threads:[~2013-12-02 3:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 20:41 [Qemu-devel] [PATCH v2] block: Close backing file early in bdrv_img_create Max Reitz
2013-11-29 22:01 ` Benoît Canet
2013-12-02 3:37 ` Wenchao Xia [this message]
2013-12-02 13:05 ` Stefan Hajnoczi
2013-12-02 10:33 ` 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=529C0080.7070106@linux.vnet.ibm.com \
--to=xiawenc@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).