From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: "M. Mohan Kumar" <mohan@in.ibm.com>,
qemu-devel@nongnu.org, Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] hw/9pfs: Fix memory leak in error path
Date: Sun, 07 Jul 2013 22:48:09 +0530 [thread overview]
Message-ID: <87vc4m9tm6.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1372929678-14341-1-git-send-email-mohan@in.ibm.com>
"M. Mohan Kumar" <mohan@in.ibm.com> writes:
> From: "M. Mohan Kumar" <mohan@in.ibm.com>
>
> Fix few more memory leaks in virtio-9p-device.c detected using valgrind.
>
> Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
> ---
> hw/9pfs/virtio-9p-device.c | 26 +++++++++++++++++---------
> 1 file changed, 17 insertions(+), 9 deletions(-)
>
> diff --git a/hw/9pfs/virtio-9p-device.c b/hw/9pfs/virtio-9p-device.c
> index dc6f4e4..35e2af4 100644
> --- a/hw/9pfs/virtio-9p-device.c
> +++ b/hw/9pfs/virtio-9p-device.c
> @@ -68,14 +68,14 @@ static int virtio_9p_device_init(VirtIODevice *vdev)
> fprintf(stderr, "Virtio-9p device couldn't find fsdev with the "
> "id = %s\n",
> s->fsconf.fsdev_id ? s->fsconf.fsdev_id : "NULL");
> - return -1;
> + goto out;
> }
>
> if (!s->fsconf.tag) {
> /* we haven't specified a mount_tag */
> fprintf(stderr, "fsdev with id %s needs mount_tag arguments\n",
> s->fsconf.fsdev_id);
> - return -1;
> + goto out;
> }
>
> s->ctx.export_flags = fse->export_flags;
> @@ -85,10 +85,10 @@ static int virtio_9p_device_init(VirtIODevice *vdev)
> if (len > MAX_TAG_LEN - 1) {
> fprintf(stderr, "mount tag '%s' (%d bytes) is longer than "
> "maximum (%d bytes)", s->fsconf.tag, len, MAX_TAG_LEN - 1);
> - return -1;
> + goto out;
> }
>
> - s->tag = strdup(s->fsconf.tag);
> + s->tag = g_strdup(s->fsconf.tag);
> s->ctx.uid = -1;
>
> s->ops = fse->ops;
> @@ -99,11 +99,11 @@ static int virtio_9p_device_init(VirtIODevice *vdev)
> if (s->ops->init(&s->ctx) < 0) {
> fprintf(stderr, "Virtio-9p Failed to initialize fs-driver with id:%s"
> " and export path:%s\n", s->fsconf.fsdev_id, s->ctx.fs_root);
> - return -1;
> + goto out;
> }
> if (v9fs_init_worker_threads() < 0) {
> fprintf(stderr, "worker thread initialization failed\n");
> - return -1;
> + goto out;
> }
>
> /*
> @@ -115,18 +115,26 @@ static int virtio_9p_device_init(VirtIODevice *vdev)
> if (s->ops->name_to_path(&s->ctx, NULL, "/", &path) < 0) {
> fprintf(stderr,
> "error in converting name to path %s", strerror(errno));
> - return -1;
> + goto out;
> }
> if (s->ops->lstat(&s->ctx, &path, &stat)) {
> fprintf(stderr, "share path %s does not exist\n", fse->path);
> - return -1;
> + goto out;
> } else if (!S_ISDIR(stat.st_mode)) {
> fprintf(stderr, "share path %s is not a directory\n", fse->path);
> - return -1;
> + goto out;
> }
> v9fs_path_free(&path);
>
> return 0;
> +out:
> + g_free(s->ctx.fs_root);
> + g_free(s->tag);
> + virtio_cleanup(vdev);
> + v9fs_path_free(&path);
> +
> + return -1;
> +
> }
>
The error path will result in qemu terminating right ? Do we care about
g_free in those case ?
-aneesh
next prev parent reply other threads:[~2013-07-07 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 9:21 [Qemu-devel] [PATCH 1/1] hw/9pfs: Fix memory leak in error path M. Mohan Kumar
2013-07-07 17:18 ` Aneesh Kumar K.V [this message]
2013-07-07 17:31 ` Andreas Färber
2013-07-10 19:33 ` Anthony Liguori
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=87vc4m9tm6.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=mohan@in.ibm.com \
--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).