qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>, Peter Xu <peterx@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Leonardo Bras <leobras@redhat.com>
Subject: [PATCH 3/8] migration: Fix possible races when shutting down the return path
Date: Mon, 18 Sep 2023 14:28:17 -0300	[thread overview]
Message-ID: <20230918172822.19052-4-farosas@suse.de> (raw)
In-Reply-To: <20230918172822.19052-1-farosas@suse.de>

We cannot call qemu_file_shutdown() on the return path file without
taking the file lock. The return path thread could be running it's
cleanup code and have just cleared the from_dst_file pointer.

Checking ms->to_dst_file for errors could also race with
migrate_fd_cleanup() which clears the to_dst_file pointer.

Protect both accesses by taking the file lock.

This was caught by inspection, it should be rare, but the next patches
will start calling this code from other places, so let's do the
correct thing.

Reviewed-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Fabiano Rosas <farosas@suse.de>
---
 migration/migration.c | 19 ++++++++++---------
 1 file changed, 10 insertions(+), 9 deletions(-)

diff --git a/migration/migration.c b/migration/migration.c
index d426b69ada..15b7258bb2 100644
--- a/migration/migration.c
+++ b/migration/migration.c
@@ -2064,17 +2064,18 @@ static int open_return_path_on_source(MigrationState *ms,
 static int await_return_path_close_on_source(MigrationState *ms)
 {
     /*
-     * If this is a normal exit then the destination will send a SHUT and the
-     * rp_thread will exit, however if there's an error we need to cause
-     * it to exit.
+     * If this is a normal exit then the destination will send a SHUT
+     * and the rp_thread will exit, however if there's an error we
+     * need to cause it to exit. shutdown(2), if we have it, will
+     * cause it to unblock if it's stuck waiting for the destination.
      */
-    if (qemu_file_get_error(ms->to_dst_file) && ms->rp_state.from_dst_file) {
-        /*
-         * shutdown(2), if we have it, will cause it to unblock if it's stuck
-         * waiting for the destination.
-         */
-        qemu_file_shutdown(ms->rp_state.from_dst_file);
+    WITH_QEMU_LOCK_GUARD(&ms->qemu_file_lock) {
+        if (ms->to_dst_file && ms->rp_state.from_dst_file &&
+            qemu_file_get_error(ms->to_dst_file)) {
+            qemu_file_shutdown(ms->rp_state.from_dst_file);
+        }
     }
+
     trace_await_return_path_close_on_source_joining();
     qemu_thread_join(&ms->rp_state.rp_thread);
     ms->rp_state.rp_thread_created = false;
-- 
2.35.3



  parent reply	other threads:[~2023-09-18 17:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 17:28 [PATCH 0/8] migration fixes Fabiano Rosas
2023-09-18 17:28 ` [PATCH 1/8] migration: Fix race that dest preempt thread close too early Fabiano Rosas
2023-09-18 17:28 ` [PATCH 2/8] migration: Fix possible race when setting rp_state.error Fabiano Rosas
2023-09-18 17:28 ` Fabiano Rosas [this message]
2023-09-18 17:28 ` [PATCH 4/8] migration: Fix possible race when shutting down to_dst_file Fabiano Rosas
2023-09-18 17:28 ` [PATCH 5/8] migration: Remove redundant cleanup of postcopy_qemufile_src Fabiano Rosas
2023-09-18 17:28 ` [PATCH 6/8] migration: Consolidate return path closing code Fabiano Rosas
2023-09-18 17:28 ` [PATCH 7/8] migration: Replace the return path retry logic Fabiano Rosas
2023-09-18 17:28 ` [PATCH 8/8] migration: Move return path cleanup to main migration thread Fabiano Rosas
2023-09-27 12:39 ` [PATCH 0/8] migration fixes Fabiano Rosas
2023-09-27 13:58   ` Peter Xu
2023-09-27 17:58 ` Stefan Hajnoczi
2023-09-27 20:14 ` Stefan Hajnoczi
2023-10-02 22:55 ` Michael Tokarev
2023-10-02 23:29   ` Peter Xu
2023-10-02 23:36     ` Michael Tokarev

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=20230918172822.19052-4-farosas@suse.de \
    --to=farosas@suse.de \
    --cc=leobras@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanha@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 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).