From: Peter Xu <peterx@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com, lvivier@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/6] migration: free addr in the same function that we created it
Date: Wed, 8 Nov 2017 16:15:10 +0800 [thread overview]
Message-ID: <20171108081510.GD2992@xz-mi> (raw)
In-Reply-To: <20171030112112.6952-4-quintela@redhat.com>
On Mon, Oct 30, 2017 at 12:21:09PM +0100, Juan Quintela wrote:
> Otherwise, we can't use it after calling socket_start_incoming_migration
>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
http://lists.gnu.org/archive/html/qemu-devel/2017-11/msg01305.html
So I got a same patch. Let's see which one will go in earlier. I think
it should be this one. :)
> ---
> migration/socket.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/migration/socket.c b/migration/socket.c
> index dee869044a..3a8232dd2d 100644
> --- a/migration/socket.c
> +++ b/migration/socket.c
> @@ -172,7 +172,6 @@ static void socket_start_incoming_migration(SocketAddress *saddr,
>
> if (qio_channel_socket_listen_sync(listen_ioc, saddr, errp) < 0) {
> object_unref(OBJECT(listen_ioc));
> - qapi_free_SocketAddress(saddr);
> return;
> }
>
> @@ -181,7 +180,6 @@ static void socket_start_incoming_migration(SocketAddress *saddr,
> socket_accept_incoming_migration,
> listen_ioc,
> (GDestroyNotify)object_unref);
> - qapi_free_SocketAddress(saddr);
> }
>
> void tcp_start_incoming_migration(const char *host_port, Error **errp)
> @@ -191,6 +189,7 @@ void tcp_start_incoming_migration(const char *host_port, Error **errp)
> if (!err) {
> socket_start_incoming_migration(saddr, &err);
> }
> + qapi_free_SocketAddress(saddr);
> error_propagate(errp, err);
> }
>
> @@ -198,4 +197,5 @@ void unix_start_incoming_migration(const char *path, Error **errp)
> {
> SocketAddress *saddr = unix_build_address(path);
> socket_start_incoming_migration(saddr, errp);
> + qapi_free_SocketAddress(saddr);
> }
> --
> 2.13.6
>
--
Peter Xu
next prev parent reply other threads:[~2017-11-08 8:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 11:21 [Qemu-devel] [PATCH 0/6] Improve info migrate output on destination Juan Quintela
2017-10-30 11:21 ` [Qemu-devel] [PATCH 1/6] qio: Make port 0 work for qio Juan Quintela
2017-10-30 20:48 ` Daniel P. Berrange
2017-11-03 9:23 ` Juan Quintela
2017-10-30 11:21 ` [Qemu-devel] [PATCH 2/6] migration: print features as on off Juan Quintela
2017-11-03 13:23 ` Dr. David Alan Gilbert
2017-11-08 8:13 ` Peter Xu
2017-10-30 11:21 ` [Qemu-devel] [PATCH 3/6] migration: free addr in the same function that we created it Juan Quintela
2017-11-08 8:15 ` Peter Xu [this message]
2017-10-30 11:21 ` [Qemu-devel] [PATCH 4/6] migration: Create uri parameter Juan Quintela
2017-10-30 11:21 ` [Qemu-devel] [PATCH 5/6] migration: Now set the migration uri Juan Quintela
2017-11-03 10:07 ` Daniel P. Berrange
2017-11-22 12:29 ` Juan Quintela
2017-11-22 12:54 ` Daniel P. Berrange
2017-11-22 12:58 ` Daniel P. Berrange
2017-11-29 16:43 ` Juan Quintela
2017-11-29 16:48 ` Daniel P. Berrange
2017-10-30 11:21 ` [Qemu-devel] [PATCH 6/6] migration: make migrate uri parameter optional Juan Quintela
2017-10-30 13:02 ` [Qemu-devel] [PATCH 0/6] Improve info migrate output on destination Fam Zheng
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=20171108081510.GD2992@xz-mi \
--to=peterx@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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.