From: "Leonardo Brás" <leobras.c@gmail.com>
To: Lukas Straub <lukasstraub2@web.de>
Cc: qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
peterx@redhat.com, Juan Quintela <quintela@redhat.com>
Subject: Re: [PATCH 1/1] yank: Unregister function when using TLS migration
Date: Wed, 26 May 2021 18:56:05 -0300 [thread overview]
Message-ID: <c0896991d6662e4d2c05c43a983e83d086a8c5c2.camel@gmail.com> (raw)
In-Reply-To: <20210526232418.2213cdc1@gecko.fritz.box>
Hello Lukas, thanks for this feedback!
On Wed, 2021-05-26 at 23:24 +0200, Lukas Straub wrote:
> > diff --git a/migration/multifd.c b/migration/multifd.c
> > index 0a4803cfcc..be8656f4c0 100644
> > --- a/migration/multifd.c
> > +++ b/migration/multifd.c
> > @@ -987,8 +987,9 @@ int multifd_load_cleanup(Error **errp)
> > for (i = 0; i < migrate_multifd_channels(); i++) {
> > MultiFDRecvParams *p = &multifd_recv_state->params[i];
> >
> > - if (object_dynamic_cast(OBJECT(p->c),
> > TYPE_QIO_CHANNEL_SOCKET)
> > - && OBJECT(p->c)->ref == 1) {
> > + if ((object_dynamic_cast(OBJECT(p->c),
> > TYPE_QIO_CHANNEL_SOCKET) ||
> > + (object_dynamic_cast(OBJECT(p->c),
> > TYPE_QIO_CHANNEL_TLS))) &&
> > + OBJECT(p->c)->ref == 1) {
> > yank_unregister_function(MIGRATION_YANK_INSTANCE,
> > migration_yank_iochannel,
> > QIO_CHANNEL(p->c));
>
> The code here should be the same as in channel_close. So for the
> tls-channel you have to unregister with QIO_CHANNEL(tioc->master)
> like
> below.
ok, sure, I will send a v2.
Thanks!
>
> Regards,
> Lukas Straub
prev parent reply other threads:[~2021-05-26 21:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 20:05 [PATCH 1/1] yank: Unregister function when using TLS migration Leonardo Bras
2021-05-26 20:40 ` Peter Xu
2021-05-26 21:21 ` Lukas Straub
2021-05-26 21:58 ` Peter Xu
2021-05-27 8:46 ` Daniel P. Berrangé
2021-05-27 12:23 ` Peter Xu
2021-05-27 12:37 ` Daniel P. Berrangé
2021-05-27 13:09 ` Peter Xu
2021-05-27 13:17 ` Daniel P. Berrangé
2021-05-27 13:34 ` Dr. David Alan Gilbert
2021-05-27 13:35 ` Peter Xu
2021-05-27 15:05 ` Lukas Straub
2021-05-26 21:24 ` Lukas Straub
2021-05-26 21:56 ` Leonardo Brás [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=c0896991d6662e4d2c05c43a983e83d086a8c5c2.camel@gmail.com \
--to=leobras.c@gmail.com \
--cc=dgilbert@redhat.com \
--cc=lukasstraub2@web.de \
--cc=peterx@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 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).