From: Stefan Hajnoczi <stefanha@gmail.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2] block: Close backing file early in bdrv_img_create
Date: Mon, 2 Dec 2013 14:05:49 +0100 [thread overview]
Message-ID: <20131202130549.GB24710@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <529C0080.7070106@linux.vnet.ibm.com>
On Mon, Dec 02, 2013 at 11:37:36AM +0800, Wenchao Xia wrote:
> 于 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;
> }
Agreed, tightening the scope of 'bs' was a good idea.
Max: can you send a final version as suggested by Wenchao?
Thanks,
Stefan
next prev parent reply other threads:[~2013-12-02 13:06 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
2013-12-02 13:05 ` Stefan Hajnoczi [this message]
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=20131202130549.GB24710@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=xiawenc@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).