All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Shannon Zhao <zhaoshenglong@huawei.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, pbonzini@redhat.com,
	shannon.zhao@linaro.org, peter.maydell@linaro.org
Subject: Re: [Qemu-trivial] [PATCH v2 0/4] Fix memory leak due to calling qemu_find_file and not freeing return buf
Date: Thu, 28 May 2015 20:47:54 +0300	[thread overview]
Message-ID: <556754CA.1090301@msgid.tls.msk.ru> (raw)
In-Reply-To: <1432816784-12436-1-git-send-email-zhaoshenglong@huawei.com>

28.05.2015 15:39, Shannon Zhao wrote:
> From: Shannon Zhao <shannon.zhao@linaro.org>
> 
> Before I sent some patches to fix memory leak spotted by valgrind. Then
> I'd like to dig deeper and find that two places have memory leak due to
> calling qemu_find_file and not freeing return buf. Then through code
> searching another two places are found. So this patchset is to fix them.

Applied all 4 to -trivial, thank you!

/mjt


WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Shannon Zhao <zhaoshenglong@huawei.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, pbonzini@redhat.com,
	shannon.zhao@linaro.org, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2 0/4] Fix memory leak due to calling qemu_find_file and not freeing return buf
Date: Thu, 28 May 2015 20:47:54 +0300	[thread overview]
Message-ID: <556754CA.1090301@msgid.tls.msk.ru> (raw)
In-Reply-To: <1432816784-12436-1-git-send-email-zhaoshenglong@huawei.com>

28.05.2015 15:39, Shannon Zhao wrote:
> From: Shannon Zhao <shannon.zhao@linaro.org>
> 
> Before I sent some patches to fix memory leak spotted by valgrind. Then
> I'd like to dig deeper and find that two places have memory leak due to
> calling qemu_find_file and not freeing return buf. Then through code
> searching another two places are found. So this patchset is to fix them.

Applied all 4 to -trivial, thank you!

/mjt

  parent reply	other threads:[~2015-05-28 17:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28 12:39 [Qemu-trivial] [PATCH v2 0/4] Fix memory leak due to calling qemu_find_file and not freeing return buf Shannon Zhao
2015-05-28 12:39 ` [Qemu-devel] " Shannon Zhao
2015-05-28 12:39 ` [Qemu-trivial] [PATCH v2 1/4] hw/display/cg3.c: Fix memory leak Shannon Zhao
2015-05-28 12:39   ` [Qemu-devel] " Shannon Zhao
2015-05-29  7:59   ` [Qemu-trivial] " Markus Armbruster
2015-05-29  7:59     ` Markus Armbruster
2015-05-28 12:39 ` [Qemu-trivial] [PATCH v2 2/4] hw/alpha/dp264.c: Fix memory leak spotted by valgrind Shannon Zhao
2015-05-28 12:39   ` [Qemu-devel] " Shannon Zhao
2015-05-28 12:39 ` [Qemu-trivial] [PATCH v2 3/4] hw/ppc/e500.c: Fix memory leak Shannon Zhao
2015-05-28 12:39   ` [Qemu-devel] " Shannon Zhao
2015-05-28 12:39 ` [Qemu-trivial] [PATCH v2 4/4] hw/display/tcx.c: Fix memory leak spotted by valgrind Shannon Zhao
2015-05-28 12:39   ` [Qemu-devel] " Shannon Zhao
2015-05-28 17:47 ` Michael Tokarev [this message]
2015-05-28 17:47   ` [Qemu-devel] [PATCH v2 0/4] Fix memory leak due to calling qemu_find_file and not freeing return buf Michael Tokarev

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=556754CA.1090301@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=shannon.zhao@linaro.org \
    --cc=zhaoshenglong@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.