From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, pkrempa@redhat.com, quintela@redhat.com,
peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Migration+TLS: Fix crash due to double cleanup
Date: Wed, 2 May 2018 13:07:05 +0100 [thread overview]
Message-ID: <20180502120705.GP3308@redhat.com> (raw)
In-Reply-To: <20180430185943.35714-1-dgilbert@redhat.com>
On Mon, Apr 30, 2018 at 07:59:43PM +0100, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>
> During a TLS connect we see:
> migration_channel_connect calls
> migration_tls_channel_connect
> (calls after TLS setup)
> migration_channel_connect
>
> My previous error handling fix made migration_channel_connect
> call migrate_fd_connect in all cases; unfortunately the above
> means it gets called twice and crashes doing double cleanup.
>
> Fixes: 688a3dcba98
>
> Reported-by: Peter Krempa <pkrempa@redhat.com>
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> migration/channel.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
I've satisfied myself that the double error reporting is not going to
cause any functional harm, so that's less urgent to fix.
>
> diff --git a/migration/channel.c b/migration/channel.c
> index c5eaf0fa0e..7a32b5aca4 100644
> --- a/migration/channel.c
> +++ b/migration/channel.c
> @@ -71,6 +71,15 @@ void migration_channel_connect(MigrationState *s,
> !object_dynamic_cast(OBJECT(ioc),
> TYPE_QIO_CHANNEL_TLS)) {
> migration_tls_channel_connect(s, ioc, hostname, &error);
> +
> + if (!error) {
> + /* tls_channel_connect will call back to this
> + * function after the TLS handshake,
> + * so we mustn't call migrate_fd_connect until then
> + */
> +
> + return;
> + }
> } else {
> QEMUFile *f = qemu_fopen_channel_output(ioc);
>
> --
> 2.17.0
>
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 :|
prev parent reply other threads:[~2018-05-02 12:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 18:59 [Qemu-devel] [PATCH] Migration+TLS: Fix crash due to double cleanup Dr. David Alan Gilbert (git)
2018-05-01 10:00 ` Daniel P. Berrangé
2018-05-01 10:11 ` Daniel P. Berrangé
2018-05-01 10:57 ` Dr. David Alan Gilbert
2018-05-01 11:21 ` Daniel P. Berrangé
2018-05-01 12:51 ` Daniel P. Berrangé
2018-05-02 12:03 ` Peter Krempa
2018-05-02 12:07 ` Daniel P. Berrangé [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=20180502120705.GP3308@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=peterx@redhat.com \
--cc=pkrempa@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).