From: Shivam Kumar <shivam.kumar1@nutanix.com>
To: qemu-devel@nongnu.org
Cc: peterx@redhat.com, farosas@suse.de,
Shivam Kumar <shivam.kumar1@nutanix.com>
Subject: [PATCH] Use multifd state to determine if multifd cleanup is needed
Date: Mon, 7 Oct 2024 15:44:51 +0000 [thread overview]
Message-ID: <20241007154451.107007-1-shivam.kumar1@nutanix.com> (raw)
If the client calls the QMP command to reset the migration
capabilities after the migration status is set to failed or cancelled
but before multifd cleanup starts, multifd cleanup can be skipped as
it will falsely assume that multifd was not used for migration. This
will eventually lead to source QEMU crashing due to the following
assertion failure:
yank_unregister_instance: Assertion `QLIST_EMPTY(&entry->yankfns)`
failed
Check multifd state to determine whether multifd was used or not for
the migration rather than checking the state of multifd migration
capability.
Signed-off-by: Shivam Kumar <shivam.kumar1@nutanix.com>
---
migration/multifd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/migration/multifd.c b/migration/multifd.c
index 9b200f4ad9..427c9a7956 100644
--- a/migration/multifd.c
+++ b/migration/multifd.c
@@ -487,7 +487,7 @@ void multifd_send_shutdown(void)
{
int i;
- if (!migrate_multifd()) {
+ if (!multifd_send_state) {
return;
}
--
2.22.3
next reply other threads:[~2024-10-07 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 15:44 Shivam Kumar [this message]
2024-10-07 16:26 ` [PATCH] Use multifd state to determine if multifd cleanup is needed Peter Xu
2024-10-08 12:09 ` Shivam Kumar
2024-10-08 14:00 ` Peter Xu
2024-10-08 14:20 ` Fabiano Rosas
2024-10-08 15:03 ` Peter Xu
2024-10-08 18:40 ` Fabiano Rosas
2024-10-09 10:02 ` Shivam Kumar
2024-10-09 13:19 ` Fabiano Rosas
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=20241007154451.107007-1-shivam.kumar1@nutanix.com \
--to=shivam.kumar1@nutanix.com \
--cc=farosas@suse.de \
--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 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).