From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Pan Nengyuan <pannengyuan@huawei.com>
Cc: zhang.zhanghailiang@huawei.com, euler.robot@huawei.com,
qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [PATCH 2/2] migration/rdma: cleanup rdma context before g_free to avoid memleaks
Date: Fri, 29 May 2020 18:27:44 +0100 [thread overview]
Message-ID: <20200529172744.GQ2856@work-vm> (raw)
In-Reply-To: <20200508100755.7875-3-pannengyuan@huawei.com>
* Pan Nengyuan (pannengyuan@huawei.com) wrote:
> When error happen in initializing 'rdma_return_path', we should cleanup rdma context
> before g_free(rdma) to avoid some memleaks. This patch fix that.
>
> Reported-by: Euler Robot <euler.robot@huawei.com>
> Signed-off-by: Pan Nengyuan <pannengyuan@huawei.com>
Queued.
> ---
> migration/rdma.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/migration/rdma.c b/migration/rdma.c
> index 72e8b1c95b..ec45d33ba3 100644
> --- a/migration/rdma.c
> +++ b/migration/rdma.c
> @@ -4094,20 +4094,20 @@ void rdma_start_outgoing_migration(void *opaque,
> rdma_return_path = qemu_rdma_data_init(host_port, errp);
>
> if (rdma_return_path == NULL) {
> - goto err;
> + goto return_path_err;
> }
>
> ret = qemu_rdma_source_init(rdma_return_path,
> s->enabled_capabilities[MIGRATION_CAPABILITY_RDMA_PIN_ALL], errp);
>
> if (ret) {
> - goto err;
> + goto return_path_err;
> }
>
> ret = qemu_rdma_connect(rdma_return_path, errp);
>
> if (ret) {
> - goto err;
> + goto return_path_err;
> }
>
> rdma->return_path = rdma_return_path;
> @@ -4120,6 +4120,8 @@ void rdma_start_outgoing_migration(void *opaque,
> s->to_dst_file = qemu_fopen_rdma(rdma, "wb");
> migrate_fd_connect(s, NULL);
> return;
> +return_path_err:
> + qemu_rdma_cleanup(rdma);
> err:
> g_free(rdma);
> g_free(rdma_return_path);
> --
> 2.18.2
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2020-05-29 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 10:07 [PATCH 0/2] migration/rdma: fix nullptr-def in rdma_start_incoming_migration Pan Nengyuan
2020-05-08 10:07 ` [PATCH 1/2] migration/rdma: fix potential nullptr access " Pan Nengyuan
2020-05-08 7:52 ` Juan Quintela
2020-05-11 9:34 ` Peter Maydell
2020-05-29 17:21 ` Dr. David Alan Gilbert
2020-05-08 10:07 ` [PATCH 2/2] migration/rdma: cleanup rdma context before g_free to avoid memleaks Pan Nengyuan
2020-05-08 7:54 ` Juan Quintela
2020-05-29 17:27 ` Dr. David Alan Gilbert [this message]
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=20200529172744.GQ2856@work-vm \
--to=dgilbert@redhat.com \
--cc=euler.robot@huawei.com \
--cc=pannengyuan@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).