From: Jeff Cody <jcody@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] sheepdog: Fix sd_co_create_opts() memory leaks
Date: Thu, 3 May 2018 12:54:10 -0400 [thread overview]
Message-ID: <20180503165410.GA6216@localhost.localdomain> (raw)
In-Reply-To: <20180503153509.22223-1-kwolf@redhat.com>
On Thu, May 03, 2018 at 05:35:09PM +0200, Kevin Wolf wrote:
> Both the option string for the 'redundancy' option and the
> SheepdogRedundancy object that is created accordingly could be leaked in
> error paths. This fixes the memory leaks.
>
> Reported by Coverity (CID 1390614 and 1390641).
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> block/sheepdog.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/block/sheepdog.c b/block/sheepdog.c
> index a2f26efc0e..6ec647e558 100644
> --- a/block/sheepdog.c
> +++ b/block/sheepdog.c
> @@ -1987,6 +1987,7 @@ static SheepdogRedundancy *parse_redundancy_str(const char *opt)
> } else {
> ret = qemu_strtol(n2, NULL, 10, &parity);
> if (ret < 0) {
> + g_free(redundancy);
> return NULL;
> }
>
> @@ -2183,7 +2184,7 @@ static int coroutine_fn sd_co_create_opts(const char *filename, QemuOpts *opts,
> QDict *qdict, *location_qdict;
> QObject *crumpled;
> Visitor *v;
> - const char *redundancy;
> + char *redundancy;
> Error *local_err = NULL;
> int ret;
>
> @@ -2253,6 +2254,7 @@ static int coroutine_fn sd_co_create_opts(const char *filename, QemuOpts *opts,
> fail:
> qapi_free_BlockdevCreateOptions(create_options);
> QDECREF(qdict);
> + g_free(redundancy);
> return ret;
> }
>
> --
> 2.13.6
>
>
Thanks,
Reviewed & applied to my block branch:
git://github.com/codyprime/qemu-kvm-jtc block
-Jeff
prev parent reply other threads:[~2018-05-03 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 15:35 [Qemu-devel] [PATCH] sheepdog: Fix sd_co_create_opts() memory leaks Kevin Wolf
2018-05-03 16:54 ` Jeff Cody [this message]
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=20180503165410.GA6216@localhost.localdomain \
--to=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).