From: Max Reitz <mreitz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH v2] block: Close backing file early in bdrv_img_create
Date: Fri, 29 Nov 2013 21:41:29 +0100 [thread overview]
Message-ID: <1385757689-23524-1-git-send-email-mreitz@redhat.com> (raw)
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(+)
diff --git a/block.c b/block.c
index 382ea71..6d571ad 100644
--- a/block.c
+++ b/block.c
@@ -4608,6 +4608,9 @@ void bdrv_img_create(const char *filename, const char *fmt,
snprintf(buf, sizeof(buf), "%" PRId64, size);
set_option_parameter(param, BLOCK_OPT_SIZE, buf);
+
+ bdrv_unref(bs);
+ bs = NULL;
} else {
error_setg(errp, "Image creation needs a size parameter");
goto out;
--
1.8.4.2
next reply other threads:[~2013-11-29 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 20:41 Max Reitz [this message]
2013-11-29 22:01 ` [Qemu-devel] [PATCH v2] block: Close backing file early in bdrv_img_create Benoît Canet
2013-12-02 3:37 ` Wenchao Xia
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=1385757689-23524-1-git-send-email-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@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).