From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Zhenyu Ye <yezhenyu2@huawei.com>
Cc: xiexiangyou@huawei.com, qemu-devel@nongnu.org,
dgilbert@redhat.com, quintela@redhat.com
Subject: Re: [PATCH v1] migration: tls: unref creds after used
Date: Tue, 21 Jul 2020 12:54:45 +0100 [thread overview]
Message-ID: <20200721115445.GG843362@redhat.com> (raw)
In-Reply-To: <20200717091943.1942-1-yezhenyu2@huawei.com>
On Fri, Jul 17, 2020 at 05:19:43PM +0800, Zhenyu Ye wrote:
> We add the reference of creds in migration_tls_get_creds(),
> but there was no place to unref it. So the OBJECT(creds) will
> never be freed and result in memory leak.
>
> Unref the creds after creating the tls-channel server/client.
>
> Signed-off-by: Zhenyu Ye <yezhenyu2@huawei.com>
> ---
> migration/tls.c | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/migration/tls.c b/migration/tls.c
> index 5171afc6c4..0740d02976 100644
> --- a/migration/tls.c
> +++ b/migration/tls.c
> @@ -97,7 +97,7 @@ void migration_tls_channel_process_incoming(MigrationState *s,
> s->parameters.tls_authz,
> errp);
> if (!tioc) {
> - return;
> + goto cleanup;
> }
>
> trace_migration_tls_incoming_handshake_start();
> @@ -107,6 +107,9 @@ void migration_tls_channel_process_incoming(MigrationState *s,
> NULL,
> NULL,
> NULL);
> +
> +cleanup:
> + object_unref(OBJECT(creds));
> }
>
>
> @@ -146,13 +149,13 @@ void migration_tls_channel_connect(MigrationState *s,
> }
> if (!hostname) {
> error_setg(errp, "No hostname available for TLS");
> - return;
> + goto cleanup;
> }
>
> tioc = qio_channel_tls_new_client(
> ioc, creds, hostname, errp);
> if (!tioc) {
> - return;
> + goto cleanup;
> }
>
> trace_migration_tls_outgoing_handshake_start(hostname);
> @@ -162,4 +165,7 @@ void migration_tls_channel_connect(MigrationState *s,
> s,
> NULL,
> NULL);
> +
> +cleanup:
> + object_unref(OBJECT(creds));
> }
Simpler to just change migration_tls_get_creds() to remove the
object_ref() call, since we're fine to use the borrowed reference
in these methods.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-07-21 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 9:19 [PATCH v1] migration: tls: unref creds after used Zhenyu Ye
2020-07-21 11:54 ` Daniel P. Berrangé [this message]
2020-07-22 3:38 ` Zhenyu Ye
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=20200721115445.GG843362@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=xiexiangyou@huawei.com \
--cc=yezhenyu2@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.