From: Pan Nengyuan <pannengyuan@huawei.com>
To: <quintela@redhat.com>, <dgilbert@redhat.com>
Cc: zhang.zhanghailiang@huawei.com,
Pan Nengyuan <pannengyuan@huawei.com>,
qemu-devel@nongnu.org, euler.robot@huawei.com
Subject: [PATCH 0/2] migration/multifd: fix two memleaks
Date: Wed, 6 May 2020 05:54:14 -0400 [thread overview]
Message-ID: <20200506095416.26099-1-pannengyuan@huawei.com> (raw)
Fix two memleaks in multifd_send_thread/multifd_new_send_channel_async when error happen.
Pan Nengyuan (2):
migration/multifd: fix memleaks in multifd_new_send_channel_async
migration/multifd: Do error_free after migrate_set_error to avoid
memleaks
migration/multifd.c | 5 +++++
1 file changed, 5 insertions(+)
--
2.18.2
next reply other threads:[~2020-05-06 3:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 9:54 Pan Nengyuan [this message]
2020-05-06 9:54 ` [PATCH 1/2] migration/multifd: fix memleaks in multifd_new_send_channel_async Pan Nengyuan
2020-05-06 8:42 ` Juan Quintela
2020-05-06 9:54 ` [PATCH 2/2] migration/multifd: Do error_free after migrate_set_error to avoid memleaks Pan Nengyuan
2020-05-06 8:43 ` Juan Quintela
2020-05-07 15:55 ` [PATCH 0/2] migration/multifd: fix two memleaks Dr. David Alan Gilbert
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=20200506095416.26099-1-pannengyuan@huawei.com \
--to=pannengyuan@huawei.com \
--cc=dgilbert@redhat.com \
--cc=euler.robot@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=zhang.zhanghailiang@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).