From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Zhenzhong Duan <zhenzhong.duan@intel.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, pbonzini@redhat.com,
Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: [PATCH] cutils: Fix memleak in get_relocated_path()
Date: Mon, 26 Apr 2021 16:06:12 +0200 [thread overview]
Message-ID: <0cf13eb3-e28b-31d4-82d1-d99636cbcaf9@redhat.com> (raw)
In-Reply-To: <20210426223042.119554-1-zhenzhong.duan@intel.com>
Hi,
On 4/27/21 12:30 AM, Zhenzhong Duan wrote:
> Valgrind complains definitely loss in get_relocated_path(), because
> GString is leaked in get_relocated_path() when returning with gchar *.
> Use g_string_free(, false) to free GString while preserving gchar *.
>
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
> ---
> util/cutils.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/util/cutils.c b/util/cutils.c
> index ee908486da..f58c2157d2 100644
> --- a/util/cutils.c
> +++ b/util/cutils.c
> @@ -1055,5 +1055,5 @@ char *get_relocated_path(const char *dir)
> assert(G_IS_DIR_SEPARATOR(dir[-1]));
> g_string_append(result, dir - 1);
> }
> - return result->str;
> + return g_string_free(result, FALSE);
> }
>
Thanks for your patch, but Stefano sent the same fix 2 weeks ago:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg798279.html
It should be merged once the development tree opens again (we are
now 'freezed' before the v6.0.0 release).
You might want to send your Review-by or Tested-by tag to Stefano's
patch.
Regards,
Phil.
next prev parent reply other threads:[~2021-04-26 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 22:30 [PATCH] cutils: Fix memleak in get_relocated_path() Zhenzhong Duan
2021-04-26 14:06 ` Philippe Mathieu-Daudé [this message]
2021-04-27 3:16 ` Duan, Zhenzhong
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=0cf13eb3-e28b-31d4-82d1-d99636cbcaf9@redhat.com \
--to=philmd@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=zhenzhong.duan@intel.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).