All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: "Juraj Marcin" <jmarcin@redhat.com>,
	peterx@redhat.com, "Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH] migration/multifd/tls: Cleanup BYE message processing on sender side
Date: Fri, 26 Sep 2025 14:40:37 -0300	[thread overview]
Message-ID: <87ikh5w1re.fsf@suse.de> (raw)
In-Reply-To: <20250925201601.290546-1-peterx@redhat.com>

Peter Xu <peterx@redhat.com> writes:

> This patch is a trivial cleanup to the BYE messages on the multifd sender
> side.  It could also be a fix, but since we do not have a solid clue,
> taking this as a cleanup only.
>
> One trivial concern is, migration_tls_channel_end() might be unsafe to be
> invoked in the migration thread if migration is not successful, because
> when failed / cancelled we do not know whether the multifd sender threads
> can be writting to the channels, while GnuTLS library (when it's a TLS
> channel) logically doesn't support concurrent writes.
>
> When at it, cleanup on a few things.  What changed:
>
>   - Introduce a helper to do graceful shutdowns with rich comment, hiding
>     the details
>
>   - Only send bye() iff migration succeeded, skip if it failed / cancelled
>
>   - Detect TLS channel using channel type rather than thread created flags
>
>   - Move the loop into the existing one that will close the channels, but
>     do graceful shutdowns before channel shutdowns
>
>   - local_err seems to have been leaked if set, fix it along the way
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
>  migration/multifd.c | 65 ++++++++++++++++++++++++---------------------
>  1 file changed, 34 insertions(+), 31 deletions(-)
>
> diff --git a/migration/multifd.c b/migration/multifd.c
> index b255778855..98873cee74 100644
> --- a/migration/multifd.c
> +++ b/migration/multifd.c
> @@ -439,6 +439,39 @@ static void multifd_send_set_error(Error *err)
>      }
>  }
>  
> +/*
> + * Gracefully shutdown IOChannels. Only needed for successful migrations on
> + * top of TLS channels.  Otherwise it is same to qio_channel_shutdown().
> + *
> + * A successful migration also guarantees multifd sender threads are

s/also//

> + * properly flushed and halted.  It is only safe to send BYE in the
> + * migration thread here when we know there's no other thread writting to

s/writting/writing/

> + * the channel, because GnuTLS doesn't support concurrent writers.
> + */
> +static void migration_ioc_shutdown_gracefully(QIOChannel *ioc)

Reviewed-by: Fabiano Rosas <farosas@suse.de>


      reply	other threads:[~2025-09-26 17:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-25 20:16 [PATCH] migration/multifd/tls: Cleanup BYE message processing on sender side Peter Xu
2025-09-26 17:40 ` Fabiano Rosas [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=87ikh5w1re.fsf@suse.de \
    --to=farosas@suse.de \
    --cc=berrange@redhat.com \
    --cc=jmarcin@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.