From: Peter Xu <peterx@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org, "Prasad Pandit" <ppandit@redhat.com>,
"Ben Chaney" <bchaney@akamai.com>,
"Juraj Marcin" <jmarcin@redhat.com>,
"Mark Kanda" <mark.kanda@oracle.com>,
"Pranav Tyagi" <prtyagi@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH] migration: Fix crash on second migration when cancel early
Date: Wed, 22 Apr 2026 11:32:40 -0400 [thread overview]
Message-ID: <aejqGMhhrfQENE1X@x1.local> (raw)
In-Reply-To: <87wlxzdsv9.fsf@suse.de>
On Wed, Apr 22, 2026 at 10:31:06AM -0300, Fabiano Rosas wrote:
> Peter Xu <peterx@redhat.com> writes:
>
> > Marc-André reported an issue on QEMU crash when retrying a cancelled
> > migration during early setup phase, see "Link:" for more information, and
> > also easy way to reproduce.
> >
> > This patch is a replacement of the prior fix proposed by not only switching
> > to migration_cleanup(), but also fixing it from CPR side, so that we track
> > hup_source properly to know if src QEMU is waiting or the HUP signal.
> >
> > To put it simple: this chunk of special casing in migration_cancel() should
> > not affect normal migration, but only cpr-transfer migration to cover the
> > small window when the src QEMU is waiting for a HUP signal on cpr
> > channel (so that src QEMU can continue the migration on the main channel).
> >
> > To achieve that, we'll also need to remember to detach the hup_source
> > whenenver invoked: after that point, we should always be able to cleanup
> > the migration.
> >
> > It's not a generic operation to explicitly detach a gsource from its
> > context while in its dispatch() function. But it should be safe, because
> > gsource disptch() will only happen with a boosted refcount for the
> > dispatcher so that the gsource will not be freed until the callback
> > completes. It's also safe to return G_SOURCE_REMOVE after the gsource is
> > detached, as glib will simply ignore the G_SOURCE_REMOVE.
> >
> > One can refer to latest 2.86.5 glib code in g_main_dispatch() for that:
> >
> > https://github.com/GNOME/glib/blob/2.86.5/glib/gmain.c#L3592
> >
> > When at this, add a bunch of assertions to make sure nothing surprises us.
> >
> > After this patch applied, the 2nd migration will not crash QEMU, instead
> > it'll be in CANCELLING until the socket connection times out (it will take
> > ~2min on my Fedora default kernel). During this process no 2nd migration
> > will be allowed, and after it timed out migration can be restarted.
> >
> > It's because so far we don't have control over socket_connect_outgoing(),
> > or anything yet managed by a task executed in qio_task_run_in_thread().
> > Speeding up the cancellation to be left for future.
[1]
> >
> > I also tested cpr-transfer by only providing cpr channel not the main
> > channel (with -incoming defer), kickoff migration on source, then cancel it
> > on source directly without providing the main channel. It keeps working.
> >
> > I wanted to add an unit test for that but it'll need to refactor current
> > cpr-transfer tests first; let's leave it for later.
> >
> > Link: https://lore.kernel.org/r/20260417184742.293061-1-marcandre.lureau@redhat.com
> > Reported-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> > Signed-off-by: Peter Xu <peterx@redhat.com>
> > ---
> > include/migration/cpr.h | 1 +
> > migration/migration.h | 5 +++++
> > migration/cpr-transfer.c | 10 ++++++++++
> > migration/migration.c | 31 +++++++++++++++++++++++--------
> > 4 files changed, 39 insertions(+), 8 deletions(-)
> >
> > diff --git a/include/migration/cpr.h b/include/migration/cpr.h
> > index 5850fd1788..ebf09a2f0a 100644
> > --- a/include/migration/cpr.h
> > +++ b/include/migration/cpr.h
> > @@ -57,6 +57,7 @@ QEMUFile *cpr_transfer_input(MigrationChannel *channel, Error **errp);
> > void cpr_transfer_add_hup_watch(MigrationState *s, QIOChannelFunc func,
> > void *opaque);
> > void cpr_transfer_source_destroy(MigrationState *s);
> > +bool cpr_transfer_source_active(MigrationState *s);
> >
> > void cpr_exec_init(void);
> > QEMUFile *cpr_exec_output(Error **errp);
> > diff --git a/migration/migration.h b/migration/migration.h
> > index b6888daced..2bc2787480 100644
> > --- a/migration/migration.h
> > +++ b/migration/migration.h
> > @@ -514,6 +514,11 @@ struct MigrationState {
> > bool postcopy_package_loaded;
> > QemuEvent postcopy_package_loaded_event;
> >
> > + /*
> > + * When set, it means cpr-transfer is waiting for the HUP signal from
> > + * destination to continue the 2nd step of migration via the main
> > + * channel.
> > + */
> > GSource *hup_source;
> >
> > /*
> > diff --git a/migration/cpr-transfer.c b/migration/cpr-transfer.c
> > index 61d5c9dce2..9defe7bad7 100644
> > --- a/migration/cpr-transfer.c
> > +++ b/migration/cpr-transfer.c
> > @@ -6,6 +6,7 @@
> > */
> >
> > #include "qemu/osdep.h"
> > +#include "qemu/main-loop.h"
> > #include "qapi/clone-visitor.h"
> > #include "qapi/error.h"
> > #include "qapi/qapi-visit-migration.h"
> > @@ -79,6 +80,7 @@ QEMUFile *cpr_transfer_input(MigrationChannel *channel, Error **errp)
> > void cpr_transfer_add_hup_watch(MigrationState *s, QIOChannelFunc func,
> > void *opaque)
> > {
> > + assert(bql_locked());
> > s->hup_source = qio_channel_create_watch(cpr_state_ioc(), G_IO_HUP);
>
> Before I review the patch in detail, let me just make a high level
> comment here:
>
> I wonder if we should have a "register" in the iochannel layer for the
> several watches we create. So we could at migration_cancel time call
Yes, we need to do this part of mgmt better either now or at some point..
Said that, just to mention: what you're discussing below seems to be about
dest QEMU, not src QEMU.
Here the "unmanaged async tasks" I mentioned above [1] is only about src
QEMU. It only applies to socket channels and socket_connect_outgoing().
It is slightly even trickier, IIUC, because instead of creating a watch
directly, it creates a pthread and run the task there, then when the task
fn() completes that thread will inject one event back to the main event
loop. See qio_task_thread_worker() and the @completion gsource.
One thing I can try to do is to work out fast cancellation for sockets here
on src side, so we don't need to wait for that 2min timeout.. But it would
still be nice to have this fix land first because it fixes a crash.. so it
may still be something on top but I can start look into. I actually don't
know how frequent users will suffer from the 2min timeout: normally when
the host:port isn't available we should just get disconnected fast.
Starting from now, I'll only discuss about dest QEMU side (IOW, may not be
directly relevant to this patch).
> g_clear_handle/g_source_destroy on all at the same time. The management
> of these source ids is getting too particular.
>
> I'm seeing that exec, fd and file migration all ignore the id returned
> by channel-watch.c. In the case of exec this is causing
> qio_channel_command_finalize() to be skipped, leaving the exec'ed
> command process behind! So what I did as an experiment was to register
Are we?
We're on the same page at least on that the gsources are not yet managed.
But I am not sure they're leaked.
exec_connect_incoming() does qio_channel_add_watch_full(), within itself it
will release the refcount of the IO watch gsource. It means it'll be a
dangling gsource on the main context. So after the spawn of the new
process, it will still be finalized properly?
> watches like this:
>
> static inline void migration_watch_data(void) {};
>
> qio_channel_add_watch_full(ioc, G_IO_IN, exec_accept_incoming_migration,
> migration_watch_data, NULL,
> g_main_context_get_thread_default());
>
> and at migrate_cancel():
>
> while(g_source_remove_by_user_data(migration_watch_data));
>
> It feels to me that a wrapper around this, or even a hashtable of "func
> ptr->GSource" or "str->GSource id" would allow us to call a (say)
> qio_channel_clear_watches() and avoid having to do the management in
> each of the clients.
In general, this whole idea sounds reasonable. I just want to check with
you on which side of QEMU we're talking about.
To me, dest QEMU is less of a concern when it can easily be killed. But
still it's good to be able to manage those. Src QEMU is more important
from that perspective.
>
> We already have stuff like IOWatchPoll which kind of already wraps the
> watch creation in a sense.
>
> > g_source_set_callback(s->hup_source,
> > (GSourceFunc)func,
> > @@ -89,9 +91,17 @@ void cpr_transfer_add_hup_watch(MigrationState *s, QIOChannelFunc func,
> >
> > void cpr_transfer_source_destroy(MigrationState *s)
> > {
> > + assert(bql_locked());
> > if (s->hup_source) {
> > g_source_destroy(s->hup_source);
> > g_source_unref(s->hup_source);
> > s->hup_source = NULL;
> > }
> > }
> > +
> > +bool cpr_transfer_source_active(MigrationState *s)
> > +{
> > + /* Whenever the HUP gsource is available, it's active. */
> > + assert(bql_locked());
> > + return s->hup_source;
> > +}
> > diff --git a/migration/migration.c b/migration/migration.c
> > index 5c9aaa6e58..58c1e56766 100644
> > --- a/migration/migration.c
> > +++ b/migration/migration.c
> > @@ -1469,14 +1469,19 @@ void migration_cancel(void)
> > }
> >
> > /*
> > - * If migration_connect_outgoing has not been called, then there
> > - * is no path that will complete the cancellation. Do it now.
> > - */
> > - if (setup && !s->to_dst_file) {
> > - migrate_set_state(&s->state, MIGRATION_STATUS_CANCELLING,
> > - MIGRATION_STATUS_CANCELLED);
> > - cpr_state_close();
> > - cpr_transfer_source_destroy(s);
> > + * This is cpr-transfer specific processing.
> > + *
> > + * If this is true, it means cpr-transfer migration is waiting for the
> > + * destination to send HUP event on CPR channel to continue the next
> > + * phase. If so, do the cleanup proactively to avoid get stuck in
> > + * CANCELLING state.
> > + */
> > + if (cpr_transfer_source_active(s)) {
> > + assert(migrate_mode() == MIG_MODE_CPR_TRANSFER);
> > + assert(setup && !s->to_dst_file);
> > + migration_cleanup(s);
> > + /* Now all things should have been released */
> > + assert(!cpr_transfer_source_active(s));
> > }
> > }
> >
> > @@ -2009,12 +2014,22 @@ static gboolean migration_connect_outgoing_cb(QIOChannel *channel,
> > MigrationState *s = migrate_get_current();
> > Error *local_err = NULL;
> >
> > + /*
> > + * Detach and release the GSource right after use. We rely on this to
> > + * detect this small cpr-transfer window of "waiting for HUP event".
> > + */
> > + cpr_transfer_source_destroy(s);
> > +
> > migration_connect_outgoing(s, opaque, &local_err);
> >
> > if (local_err) {
> > migration_connect_error_propagate(s, local_err);
> > }
> >
> > + /*
> > + * This is redundant as we do cpr_transfer_source_destroy() at the
> > + * entry, but it's benign; glib will just skip the detach.
> > + */
> > return G_SOURCE_REMOVE;
> > }
>
--
Peter Xu
next prev parent reply other threads:[~2026-04-22 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 17:58 [PATCH] migration: Fix crash on second migration when cancel early Peter Xu
2026-04-22 13:31 ` Fabiano Rosas
2026-04-22 14:14 ` Fabiano Rosas
2026-04-22 15:32 ` Peter Xu [this message]
2026-04-22 21:52 ` Fabiano Rosas
2026-04-23 15:25 ` Peter Xu
2026-05-06 20:51 ` Fabiano Rosas
2026-05-07 17:23 ` 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=aejqGMhhrfQENE1X@x1.local \
--to=peterx@redhat.com \
--cc=bchaney@akamai.com \
--cc=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=jmarcin@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mark.kanda@oracle.com \
--cc=ppandit@redhat.com \
--cc=prtyagi@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.