From: Fabiano Rosas <farosas@suse.de>
To: qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>, Peter Xu <peterx@redhat.com>,
Wei Wang <wei.w.wang@intel.com>
Subject: [PATCH v5 0/8] Fix segfault on migration return path
Date: Thu, 31 Aug 2023 15:39:08 -0300 [thread overview]
Message-ID: <20230831183916.13203-1-farosas@suse.de> (raw)
What was left from v4 was to figure out how to pair the yank
register/unregister for the QEMUFiles.
I noticed that we don't really need to call unregister_yank under the
lock. We just need to make sure the pointer is still valid. So I went
with Peter's first suggestion which was to call the function
individually for the QIOChannels we know yank is registered.
CI run: https://gitlab.com/farosas/qemu/-/pipelines/988224440
v4:
https://lore.kernel.org/r/20230816142510.5637-1-farosas@suse.de
v3:
https://lore.kernel.org/r/20230811150836.2895-1-farosas@suse.de
v2:
https://lore.kernel.org/r/20230802143644.7534-1-farosas@suse.de
v1:
https://lore.kernel.org/r/20230728121516.16258-1-farosas@suse.de
Fabiano Rosas (8):
migration: Fix possible race when setting rp_state.error
migration: Fix possible races when shutting down the return path
migration: Fix possible race when shutting down to_dst_file
migration: Remove redundant cleanup of postcopy_qemufile_src
migration: Consolidate return path closing code
migration: Replace the return path retry logic
migration: Move return path cleanup to main migration thread
migration: Add a wrapper to cleanup migration files
migration/migration.c | 231 +++++++++++++------------------------
migration/migration.h | 1 -
migration/yank_functions.c | 5 +
3 files changed, 88 insertions(+), 149 deletions(-)
--
2.35.3
next reply other threads:[~2023-08-31 18:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 18:39 Fabiano Rosas [this message]
2023-08-31 18:39 ` [PATCH v5 1/8] migration: Fix possible race when setting rp_state.error Fabiano Rosas
2023-08-31 18:39 ` [PATCH v5 2/8] migration: Fix possible races when shutting down the return path Fabiano Rosas
2023-08-31 18:39 ` [PATCH v5 3/8] migration: Fix possible race when shutting down to_dst_file Fabiano Rosas
2023-08-31 18:39 ` [PATCH v5 4/8] migration: Remove redundant cleanup of postcopy_qemufile_src Fabiano Rosas
2023-08-31 18:39 ` [PATCH v5 5/8] migration: Consolidate return path closing code Fabiano Rosas
2023-08-31 18:39 ` [PATCH v5 6/8] migration: Replace the return path retry logic Fabiano Rosas
2023-08-31 18:39 ` [PATCH v5 7/8] migration: Move return path cleanup to main migration thread Fabiano Rosas
2023-08-31 18:39 ` [PATCH v5 8/8] migration: Add a wrapper to cleanup migration files Fabiano Rosas
2023-09-01 16:05 ` Peter Xu
2023-09-01 18:29 ` Fabiano Rosas
2023-09-05 15:34 ` Peter Xu
2023-09-05 17:25 ` 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=20230831183916.13203-1-farosas@suse.de \
--to=farosas@suse.de \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=wei.w.wang@intel.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.