From: Laszlo Ersek <lersek@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] blkdebug: Don't leak bs->file on failure
Date: Sat, 08 Feb 2014 10:46:32 +0100 [thread overview]
Message-ID: <52F5FCF8.2070107@redhat.com> (raw)
In-Reply-To: <1391849670-10352-1-git-send-email-kwolf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2092 bytes --]
comments below
On 02/08/14 09:54, Kevin Wolf wrote:
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> block/blkdebug.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/block/blkdebug.c b/block/blkdebug.c
> index 56c4cd0..519b483 100644
> --- a/block/blkdebug.c
> +++ b/block/blkdebug.c
> @@ -414,7 +414,7 @@ static int blkdebug_open(BlockDriverState *bs, QDict *options, int flags,
> flags, true, false, &local_err);
> if (ret < 0) {
> error_propagate(errp, local_err);
> - goto fail;
> + goto fail_unref;
> }
This block appears to run when the bdrv_open_image(&bs->file, ...) call
fails. If we can't open the backing file, are you sure we need to unref
it under fail_unref? I thought that this block needed no update (one
only needs to extend the error handling when allocation of a new
resource is successful), but I may have been wrong of course. (Generally
in qemu it's always anyone's best guess who is responsible for releasing
stuff on the error path, caller or callee.)
>
> /* Set request alignment */
> @@ -424,10 +424,13 @@ static int blkdebug_open(BlockDriverState *bs, QDict *options, int flags,
> } else {
> error_setg(errp, "Invalid alignment");
> ret = -EINVAL;
> - goto fail;
> + goto fail_unref;
> }
I do agree with this.
>
> - ret = 0;
> + return 0;
> +
> +fail_unref:
> + bdrv_unref(bs->file);
> fail:
> qemu_opts_del(opts);
> return ret;
>
I believe this change causes us to leak "opts" on success.
... Unless we should have hung on to it to begin with, of course, in
which case this is a silent bugfix. But I don't believe so; I think we
only need "opts" temporarily, to absorb options from the QDict, and for
ease of parsing into local variables.
How about the attached patch instead? Releasing stuff in specific error
handler blocks quickly becomes intractable if there are many resources
to allocate in succession, but in this case I think we can easily get
away with it.
Thanks,
Laszlo
[-- Attachment #2: blkdebug_open.patch --]
[-- Type: text/plain, Size: 1300 bytes --]
diff --git a/block/blkdebug.c b/block/blkdebug.c
index 56c4cd0..1a8ccc4 100644
--- a/block/blkdebug.c
+++ b/block/blkdebug.c
@@ -396,14 +396,14 @@ static int blkdebug_open(BlockDriverState *bs, QDict *options, int flags,
if (error_is_set(&local_err)) {
error_propagate(errp, local_err);
ret = -EINVAL;
- goto fail;
+ goto done;
}
/* Read rules from config file or command line options */
config = qemu_opt_get(opts, "config");
ret = read_config(s, config, options, errp);
if (ret) {
- goto fail;
+ goto done;
}
/* Set initial state */
@@ -414,7 +414,7 @@ static int blkdebug_open(BlockDriverState *bs, QDict *options, int flags,
flags, true, false, &local_err);
if (ret < 0) {
error_propagate(errp, local_err);
- goto fail;
+ goto done;
}
/* Set request alignment */
@@ -423,12 +423,13 @@ static int blkdebug_open(BlockDriverState *bs, QDict *options, int flags,
bs->request_alignment = align;
} else {
error_setg(errp, "Invalid alignment");
+ bdrv_unref(bs->file);
ret = -EINVAL;
- goto fail;
+ goto done;
}
ret = 0;
-fail:
+done:
qemu_opts_del(opts);
return ret;
}
next prev parent reply other threads:[~2014-02-08 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 8:54 [Qemu-devel] [PATCH] blkdebug: Don't leak bs->file on failure Kevin Wolf
2014-02-08 9:46 ` Laszlo Ersek [this message]
2014-02-08 9:55 ` Kevin Wolf
2014-02-08 9:57 ` Laszlo Ersek
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=52F5FCF8.2070107@redhat.com \
--to=lersek@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).