From: Lukas Straub <lukasstraub2@web.de>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Leonardo Bras <leobras.c@gmail.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [PATCH 1/1] yank: Unregister function when using TLS migration
Date: Wed, 26 May 2021 23:21:03 +0200 [thread overview]
Message-ID: <20210526232103.39e2a7d0@gecko.fritz.box> (raw)
In-Reply-To: <YK6yQ9EVNlVPDMaS@t490s>
[-- Attachment #1: Type: text/plain, Size: 1849 bytes --]
On Wed, 26 May 2021 16:40:35 -0400
Peter Xu <peterx@redhat.com> wrote:
> On Wed, May 26, 2021 at 05:05:40PM -0300, Leonardo Bras wrote:
> > After yank feature was introduced, whenever migration is started using TLS,
> > the following error happens in both source and destination hosts:
> >
> > (qemu) qemu-kvm: ../util/yank.c:107: yank_unregister_instance:
> > Assertion `QLIST_EMPTY(&entry->yankfns)' failed.
> >
> > This happens because of a missing yank_unregister_function() when using
> > qio-channel-tls.
> >
> > Fix this by also allowing TYPE_QIO_CHANNEL_TLS object type to perform
> > yank_unregister_function() in channel_close() and multifd_load_cleanup().
> >
> > Fixes: 50186051f ("Introduce yank feature")
> > Buglink: https://bugzilla.redhat.com/show_bug.cgi?id=1964326
> > Signed-off-by: Leonardo Bras <leobras.c@gmail.com>
>
> Leo,
>
> Thanks for looking into it!
>
> So before looking int the fix... I do have a doubt on why we only enable yank
> on socket typed, as I think tls should also work with qio_channel_shutdown().
>
> IIUC the confused thing here is we register only for qio-socket, however tls
> will actually call migration_channel_connect() twice, first with a qio-socket,
> then with the real tls-socket. For tls I feel like we have registered with the
> wrong channel - instead of the wrapper socket ioc, we should register to the
> final tls ioc?
>
> Lukas, is there a reason?
>
Hi,
There is no specific reason. Both ways work equally well in preventing
qemu from hanging. shutdown() for tls-channel just makes it abort a
little sooner (by not attempting to encrypt and send data anymore).
I don't lean either way. I guess registering it on the tls-channel
makes is a bit more explicit and clearer.
What do you think?
Regards,
Lukas Straub
--
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-05-26 21:37 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 [this message]
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
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=20210526232103.39e2a7d0@gecko.fritz.box \
--to=lukasstraub2@web.de \
--cc=dgilbert@redhat.com \
--cc=leobras.c@gmail.com \
--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).