From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Li Xiaohui <xiaohli@redhat.com>,
Lukas Straub <lukasstraub2@web.de>,
qemu-devel@nongnu.org,
Leonardo Bras Soares Passos <lsoaresp@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [PATCH 2/3] migration: Don't do migrate cleanup if during postcopy resume
Date: Mon, 12 Jul 2021 19:33:40 +0100 [thread overview]
Message-ID: <YOyLBA89pUWPq9LU@work-vm> (raw)
In-Reply-To: <20210708190653.252961-3-peterx@redhat.com>
* Peter Xu (peterx@redhat.com) wrote:
> Below process could crash qemu with postcopy recovery:
>
> 1. (hmp) migrate -d ..
> 2. (hmp) migrate_start_postcopy
> 3. [network down, postcopy paused]
> 4. (hmp) migrate -r $WRONG_PORT
> when try the recover on an invalid $WRONG_PORT, cleanup_bh will be cleared
> 5. (hmp) migrate -r $RIGHT_PORT
> [qemu crash on assert(cleanup_bh)]
>
> The thing is we shouldn't cleanup if it's postcopy resume; the error is set
> mostly because the channel is wrong, so we return directly waiting for the user
> to retry.
>
> migrate_fd_cleanup() should only be called when migration is cancelled or
> completed.
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> migration/migration.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/migration/migration.c b/migration/migration.c
> index 8786104c9a..bb1edf862a 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -3975,7 +3975,18 @@ void migrate_fd_connect(MigrationState *s, Error *error_in)
> }
> if (error_in) {
> migrate_fd_error(s, error_in);
> - migrate_fd_cleanup(s);
> + if (resume) {
> + /*
> + * Don't do cleanup for resume if channel is invalid, but only dump
> + * the error. We wait for another channel connect from the user.
> + * The error_report still gives HMP user a hint on what failed.
> + * It's normally done in migrate_fd_cleanup(), but call it here
> + * explicitly.
> + */
> + error_report_err(error_copy(s->error));
> + } else {
> + migrate_fd_cleanup(s);
> + }
> return;
> }
>
> --
> 2.31.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2021-07-12 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 19:06 [PATCH 0/3] migration: Three more fixes for postcopy recovery Peter Xu
2021-07-08 19:06 ` [PATCH 1/3] migration: Release return path early for paused postcopy Peter Xu
2021-07-08 19:13 ` Peter Xu
2021-07-12 17:44 ` Dr. David Alan Gilbert
2021-07-08 19:06 ` [PATCH 2/3] migration: Don't do migrate cleanup if during postcopy resume Peter Xu
2021-07-12 18:33 ` Dr. David Alan Gilbert [this message]
2021-07-08 19:06 ` [PATCH 3/3] migration: Clear error at entry of migrate_fd_connect() Peter Xu
2021-07-12 18:40 ` Dr. David Alan Gilbert
2021-07-13 11:04 ` [PATCH 0/3] migration: Three more fixes for postcopy recovery Dr. David Alan Gilbert
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=YOyLBA89pUWPq9LU@work-vm \
--to=dgilbert@redhat.com \
--cc=lsoaresp@redhat.com \
--cc=lukasstraub2@web.de \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=xiaohli@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.