From: Liam Merwick <liam.merwick@oracle.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: mreitz@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vvfat: Fix memory leak
Date: Wed, 14 Nov 2018 14:50:47 +0000 [thread overview]
Message-ID: <9afd325c-5af6-e154-936e-61557d85822a@oracle.com> (raw)
In-Reply-To: <20181114125546.4319-1-kwolf@redhat.com>
On 14/11/2018 12:55, Kevin Wolf wrote:
> Don't leak 'cluster' in the mapping == NULL case. Found by Coverity
> (CID 1055918).
>
> Fixes: 8d9401c2791ee2d2805b741b1ee3006041edcd3e
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Liam Merwick <liam.merwick@oracle.com>
Thanks.
> ---
> block/vvfat.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/block/vvfat.c b/block/vvfat.c
> index 1de5de1db4..b7b61ea8b7 100644
> --- a/block/vvfat.c
> +++ b/block/vvfat.c
> @@ -2510,7 +2510,7 @@ static int commit_one_file(BDRVVVFATState* s,
> uint32_t first_cluster = c;
> mapping_t* mapping = find_mapping_for_cluster(s, c);
> uint32_t size = filesize_of_direntry(direntry);
> - char* cluster = g_malloc(s->cluster_size);
> + char *cluster;
> uint32_t i;
> int fd = 0;
>
> @@ -2528,17 +2528,17 @@ static int commit_one_file(BDRVVVFATState* s,
> if (fd < 0) {
> fprintf(stderr, "Could not open %s... (%s, %d)\n", mapping->path,
> strerror(errno), errno);
> - g_free(cluster);
> return fd;
> }
> if (offset > 0) {
> if (lseek(fd, offset, SEEK_SET) != offset) {
> qemu_close(fd);
> - g_free(cluster);
> return -3;
> }
> }
>
> + cluster = g_malloc(s->cluster_size);
> +
> while (offset < size) {
> uint32_t c1;
> int rest_size = (size - offset > s->cluster_size ?
>
prev parent reply other threads:[~2018-11-14 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 12:55 [Qemu-devel] [PATCH] vvfat: Fix memory leak Kevin Wolf
2018-11-14 13:28 ` Philippe Mathieu-Daudé
2018-11-14 14:50 ` Liam Merwick [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=9afd325c-5af6-e154-936e-61557d85822a@oracle.com \
--to=liam.merwick@oracle.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).