qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>, qemu-devel@nongnu.org
Cc: Hannes Reinecke <hare@suse.com>, Fam Zheng <famz@redhat.com>,
	qemu-block@nongnu.org,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 2/4] tests: fix bdrv-drain leak
Date: Mon, 13 Aug 2018 17:36:54 +0200	[thread overview]
Message-ID: <a7f2ed18-2e31-00a3-e68f-7b21c18361ee@redhat.com> (raw)
In-Reply-To: <20180809114417.28718-3-marcandre.lureau@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]

On 2018-08-09 13:44, Marc-André Lureau wrote:
> Spotted by ASAN:
> 
> =================================================================
> ==5378==ERROR: LeakSanitizer: detected memory leaks
> 
> Direct leak of 65536 byte(s) in 1 object(s) allocated from:
>     #0 0x7f788f83bc48 in malloc (/lib64/libasan.so.5+0xeec48)
>     #1 0x7f788c9923c5 in g_malloc (/lib64/libglib-2.0.so.0+0x523c5)
>     #2 0x5622a1fe37bc in coroutine_trampoline /home/elmarco/src/qq/util/coroutine-ucontext.c:116
>     #3 0x7f788a15d75f in __correctly_grouped_prefixwc (/lib64/libc.so.6+0x4c75f)
> 
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> ---
>  tests/test-bdrv-drain.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/tests/test-bdrv-drain.c b/tests/test-bdrv-drain.c
> index 17bb8508ae..abc8bbe6f0 100644
> --- a/tests/test-bdrv-drain.c
> +++ b/tests/test-bdrv-drain.c
> @@ -948,6 +948,7 @@ static void coroutine_fn test_co_delete_by_drain(void *opaque)
>      }
>  
>      dbdd->done = true;
> +    g_free(buffer);
>  }
>  
>  /**
> 

Thanks, added a note of the commit that broke it to the commit message
and applied to my block branch:

https://git.xanclic.moe/XanClic/qemu/commits/branch/block

Max


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2018-08-13 15:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-09 11:44 [Qemu-devel] [PATCH 0/4] Memory leak fixes Marc-André Lureau
2018-08-09 11:44 ` [Qemu-devel] [PATCH 1/4] tests: fix crumple/recursive leak Marc-André Lureau
2018-08-10  6:25   ` Markus Armbruster
2018-08-09 11:44 ` [Qemu-devel] [PATCH 2/4] tests: fix bdrv-drain leak Marc-André Lureau
2018-08-10  6:28   ` Markus Armbruster
2018-08-11 14:03     ` Max Reitz
2018-08-13  6:15       ` Markus Armbruster
2018-08-13 15:35         ` Max Reitz
2018-08-14  4:36           ` Markus Armbruster
2018-08-13 15:36   ` Max Reitz [this message]
2018-08-09 11:44 ` [Qemu-devel] [PATCH 3/4] monitor: fix oob command leak Marc-André Lureau
2018-08-09 14:38   ` Marc-André Lureau
2018-08-10  6:55     ` Markus Armbruster
2018-08-09 11:44 ` [Qemu-devel] [PATCH 4/4] RFC: fix megasas leak Marc-André Lureau
2018-08-14  6:26   ` Paolo Bonzini
2018-08-09 16:45 ` [Qemu-devel] [PATCH 0/4] Memory leak fixes Eric Blake

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=a7f2ed18-2e31-00a3-e68f-7b21c18361ee@redhat.com \
    --to=mreitz@redhat.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=famz@redhat.com \
    --cc=hare@suse.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@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).