From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] migration: fix crash in when incoming client channel setup fails
Date: Tue, 19 Jun 2018 16:45:05 +0100 [thread overview]
Message-ID: <20180619154504.GI2368@work-vm> (raw)
In-Reply-To: <20180619151719.17002-1-berrange@redhat.com>
* Daniel P. Berrangé (berrange@redhat.com) wrote:
> The way we determine if we can start the incoming migration was
> changed to use migration_has_all_channels() in:
>
> commit 428d89084c709e568f9cd301c2f6416a54c53d6d
> Author: Juan Quintela <quintela@redhat.com>
> Date: Mon Jul 24 13:06:25 2017 +0200
>
> migration: Create migration_has_all_channels
>
> This method in turn calls multifd_recv_all_channels_created()
> which is hardcoded to always return 'true' when multifd is
> not in use.
>
> This means that if channel initialization fails with normal
> migration, it'll never notice and attempt to start the
> incoming migration regardless.
I'm not sure if that was actually the cause, because older versions
had no check at all in socket_accept_incoming_migration.
> This can be seen, for example, if a client connects to a server
> requiring TLS, but has an invalid x509 certificate:
>
> qemu-system-x86_64: The certificate hasn't got a known issuer
> qemu-system-x86_64: migration/migration.c:386: process_incoming_migration_co: Assertion `mis->from_src_file' failed.
>
> #0 0x00007fffebd24f2b in raise () at /lib64/libc.so.6
> #1 0x00007fffebd0f561 in abort () at /lib64/libc.so.6
> #2 0x00007fffebd0f431 in _nl_load_domain.cold.0 () at /lib64/libc.so.6
> #3 0x00007fffebd1d692 in () at /lib64/libc.so.6
> #4 0x0000555555ad027e in process_incoming_migration_co (opaque=<optimized out>) at migration/migration.c:386
> #5 0x0000555555c45e8b in coroutine_trampoline (i0=<optimized out>, i1=<optimized out>) at util/coroutine-ucontext.c:116
> #6 0x00007fffebd3a6a0 in __start_context () at /lib64/libc.so.6
> #7 0x0000000000000000 in ()
>
> To handle the non-multifd case, we check whether mis->from_src_file
> is non-NULL.
So, what happens with this fix, does the destination exit cleanly, or
stay to accept another connection or what?
Dave
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> migration/migration.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/migration/migration.c b/migration/migration.c
> index e1eaa97df4..38ad818b23 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -518,11 +518,12 @@ void migration_ioc_process_incoming(QIOChannel *ioc)
> */
> bool migration_has_all_channels(void)
> {
> + MigrationIncomingState *mis = migration_incoming_get_current();
> bool all_channels;
>
> all_channels = multifd_recv_all_channels_created();
>
> - return all_channels;
> + return all_channels && mis->from_src_file != NULL;
> }
>
> /*
> --
> 2.17.0
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-06-19 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 15:17 [Qemu-devel] [PATCH] migration: fix crash in when incoming client channel setup fails Daniel P. Berrangé
2018-06-19 15:45 ` Dr. David Alan Gilbert [this message]
2018-06-19 15:58 ` Daniel P. Berrangé
2018-06-19 16:00 ` Dr. David Alan Gilbert
2018-06-19 16:02 ` Daniel P. Berrangé
2018-06-19 16:28 ` Daniel P. Berrangé
2018-06-19 16:31 ` Eric Blake
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=20180619154504.GI2368@work-vm \
--to=dgilbert@redhat.com \
--cc=berrange@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).