From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Leonardo Bras <leobras@redhat.com>
Cc: armbru@redhat.com, qemu-devel@nongnu.org,
Peter Xu <peterx@redhat.com>, Juan Quintela <quintela@redhat.com>
Subject: Re: [PATCH v2 1/1] migration: Unregister yank if migration setup fails
Date: Tue, 29 Jun 2021 10:25:03 +0100 [thread overview]
Message-ID: <YNrm7+QyoIXDd7C4@work-vm> (raw)
In-Reply-To: <20210629050522.147057-1-leobras@redhat.com>
* Leonardo Bras (leobras@redhat.com) wrote:
> Currently, if a qemu instance is started with "-incoming defer" and
> an incorect parameter is passed to "migrate_incoming", it will print the
> expected error and reply with "duplicate yank instance" for any upcoming
> "migrate_incoming" command.
>
> This renders current qemu process unusable, and requires a new qemu
> process to be started before accepting a migration.
>
> This is caused by a yank_register_instance() that happens in
> qemu_start_incoming_migration() but is never reverted if any error
> happens.
>
> Solves this by unregistering the instance if anything goes wrong
> in the function, allowing a new "migrate_incoming" command to be
> accepted.
>
> Fixes: b5eea99ec2f ("migration: Add yank feature", 2021-01-13)
> Buglink: https://bugzilla.redhat.com/show_bug.cgi?id=1974366
> Signed-off-by: Leonardo Bras <leobras@redhat.com>
> Reviewed-by: Peter Xu <peterx@redhat.com>
>
> ---
> Changes since v1:
> - Add ERRP_GUARD() at the beginning of the function, so it deals with
> errp passed as NULL, and does correct error propagation.
Thanks;
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> migration/migration.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/migration/migration.c b/migration/migration.c
> index 4228635d18..af0c72609f 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -454,6 +454,7 @@ void migrate_add_address(SocketAddress *address)
>
> static void qemu_start_incoming_migration(const char *uri, Error **errp)
> {
> + ERRP_GUARD();
> const char *p = NULL;
>
> if (!yank_register_instance(MIGRATION_YANK_INSTANCE, errp)) {
> @@ -474,9 +475,13 @@ static void qemu_start_incoming_migration(const char *uri, Error **errp)
> } else if (strstart(uri, "fd:", &p)) {
> fd_start_incoming_migration(p, errp);
> } else {
> - yank_unregister_instance(MIGRATION_YANK_INSTANCE);
> error_setg(errp, "unknown migration protocol: %s", uri);
> }
> +
> + if (*errp) {
> + yank_unregister_instance(MIGRATION_YANK_INSTANCE);
> + }
> +
> }
>
> static void process_incoming_migration_bh(void *opaque)
> --
> 2.32.0
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2021-06-29 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 5:05 [PATCH v2 1/1] migration: Unregister yank if migration setup fails Leonardo Bras
2021-06-29 9:25 ` Dr. David Alan Gilbert [this message]
2021-06-29 16:51 ` Peter Xu
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=YNrm7+QyoIXDd7C4@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=leobras@redhat.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 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.