qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Yan Wang <wangyan122@huawei.com>, groug@kaod.org
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] 9p: local: fix memory leak
Date: Mon, 30 Dec 2019 09:35:11 +0100	[thread overview]
Message-ID: <c387271b-ff01-edc9-e3d8-82989cc12cb6@redhat.com> (raw)
In-Reply-To: <20191230022347.36932-1-wangyan122@huawei.com>

Please describe the memory leak, and if possible how you noticed it.

Indeed the previous 2 calls to g_path_get_dirname() aren't free'd.

On 12/30/19 3:23 AM, Yan Wang wrote:
> Signed-off-by: Yan Wang <wangyan122@huawei.com>
> ---
>   hw/9pfs/9p-local.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/hw/9pfs/9p-local.c b/hw/9pfs/9p-local.c
> index ca641390fb..d0592c3b45 100644
> --- a/hw/9pfs/9p-local.c
> +++ b/hw/9pfs/9p-local.c
> @@ -947,7 +947,7 @@ static int local_link(FsContext *ctx, V9fsPath *oldpath,
>       if (ctx->export_flags & V9FS_SM_MAPPED_FILE &&
>           local_is_mapped_file_metadata(ctx, name)) {
>           errno = EINVAL;
> -        return -1;
> +        goto out;

As the rest of this function... OK.
With some love this function could get clever by only allocating 
variables it will use.

With better commit description:
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>

>       }
>   
>       odirfd = local_opendir_nofollow(ctx, odirpath);
> 



  reply	other threads:[~2019-12-30  8:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-30  2:23 [PATCH] 9p: local: fix memory leak Yan Wang
2019-12-30  8:35 ` Philippe Mathieu-Daudé [this message]
2019-12-30 11:34 ` Christian Schoenebeck
2020-01-06 10:54   ` Greg Kurz

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=c387271b-ff01-edc9-e3d8-82989cc12cb6@redhat.com \
    --to=philmd@redhat.com \
    --cc=groug@kaod.org \
    --cc=qemu-devel@nongnu.org \
    --cc=wangyan122@huawei.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).