From: Fam Zheng <famz@redhat.com>
To: "Benoît Canet" <benoit.canet@irqsave.net>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 4/4] qcow2: Fix leak of opts in qcow2_open
Date: Thu, 28 Aug 2014 12:04:22 +0800 [thread overview]
Message-ID: <20140828040422.GD15156@T430.redhat.com> (raw)
In-Reply-To: <20140827144036.GI31176@irqsave.net>
On Wed, 08/27 16:40, Benoît Canet wrote:
> The Wednesday 27 Aug 2014 à 14:02:36 (+0800), Fam Zheng wrote :
> > Not all the error paths release opts, fix it by moving it after the fail
> > label.
> >
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > ---
> > block/qcow2.c | 5 ++---
> > 1 file changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git a/block/qcow2.c b/block/qcow2.c
> > index f9e045f..b4c4a6e 100644
> > --- a/block/qcow2.c
> > +++ b/block/qcow2.c
> > @@ -535,7 +535,7 @@ static int qcow2_open(BlockDriverState *bs, QDict *options, int flags,
> > unsigned int len, i;
> > int ret = 0;
> > QCowHeader header;
> > - QemuOpts *opts;
> > + QemuOpts *opts = NULL;
> > Error *local_err = NULL;
> > uint64_t ext_end;
> > uint64_t l1_vm_state_index;
> > @@ -932,7 +932,6 @@ static int qcow2_open(BlockDriverState *bs, QDict *options, int flags,
> > error_setg(errp, "Unsupported value '%s' for qcow2 option "
> > "'overlap-check'. Allowed are either of the following: "
> > "none, constant, cached, all", opt_overlap_check);
> > - qemu_opts_del(opts);
> > ret = -EINVAL;
> > goto fail;
> > }
> > @@ -946,7 +945,6 @@ static int qcow2_open(BlockDriverState *bs, QDict *options, int flags,
> > overlap_check_template & (1 << i)) << i;
> > }
> >
> > - qemu_opts_del(opts);
> >
> > if (s->use_lazy_refcounts && s->qcow_version < 3) {
> > error_setg(errp, "Lazy refcounts require a qcow2 image with at least "
> > @@ -964,6 +962,7 @@ static int qcow2_open(BlockDriverState *bs, QDict *options, int flags,
>
>
> > return ret;
> The code is returning here in this case and the qemu_opts_del is hidden in the fail label.
> Do we need to qemu_opts_del on success just before return like it was done before ?
Yes, good catch.
Thanks,
Fam
>
> >
> > fail:
> > + qemu_opts_del(opts);
> > g_free(s->unknown_header_fields);
> > cleanup_unknown_header_ext(bs);
> > qcow2_free_snapshots(bs);
> > --
> > 2.1.0
> >
> >
next prev parent reply other threads:[~2014-08-28 4:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 6:02 [Qemu-devel] [PATCH 0/4] block: Fix leaks of opts in block drivers Fam Zheng
2014-08-27 6:02 ` [Qemu-devel] [PATCH 1/4] nfs: Fix leak of opts in nfs_file_open Fam Zheng
2014-08-27 14:46 ` Benoît Canet
2014-08-28 4:07 ` Fam Zheng
2014-08-27 6:02 ` [Qemu-devel] [PATCH 2/4] blkverify: Fix leak of opts in blkverify_open Fam Zheng
2014-08-27 14:41 ` Benoît Canet
2014-08-27 6:02 ` [Qemu-devel] [PATCH 3/4] quorum: Fix leak of opts in quorum_open Fam Zheng
2014-08-27 14:36 ` Benoît Canet
2014-08-27 6:02 ` [Qemu-devel] [PATCH 4/4] qcow2: Fix leak of opts in qcow2_open Fam Zheng
2014-08-27 14:40 ` Benoît Canet
2014-08-28 4:04 ` Fam Zheng [this message]
2014-08-27 17:40 ` Max Reitz
2014-08-28 4:06 ` Fam Zheng
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=20140828040422.GD15156@T430.redhat.com \
--to=famz@redhat.com \
--cc=benoit.canet@irqsave.net \
--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).