6d3351
From 4b3819d67eaf7c9ed31a2d306968d24fecae68ea Mon Sep 17 00:00:00 2001
6d3351
Message-Id: <4b3819d67eaf7c9ed31a2d306968d24fecae68ea@dist-git>
6d3351
From: Jiri Denemark <jdenemar@redhat.com>
6d3351
Date: Wed, 5 Apr 2017 12:04:09 +0200
6d3351
Subject: [PATCH] qemu: Always reset TLS in qemuProcessRecoverMigrationOut
6d3351
6d3351
qemuProcessRecoverMigrationOut doesn't explicitly call
6d3351
qemuMigrationResetTLS relying on two things:
6d3351
6d3351
    - qemuMigrationCancel resets TLS parameters
6d3351
    - our migration code resets TLS before entering
6d3351
      QEMU_MIGRATION_PHASE_PERFORM3_DONE phase
6d3351
6d3351
But this is not obvious and the assumptions will be broken soon. Let's
6d3351
explicitly reset TLS parameters on all paths which do not kill the
6d3351
domain.
6d3351
6d3351
Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
6d3351
(cherry picked from commit 9d677e6a6ba075f489f791b6922a5dadf0e0c79f)
6d3351
6d3351
https://bugzilla.redhat.com/show_bug.cgi?id=1425003
6d3351
6d3351
Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
6d3351
---
6d3351
 src/qemu/qemu_process.c | 1 +
6d3351
 1 file changed, 1 insertion(+)
6d3351
6d3351
diff --git a/src/qemu/qemu_process.c b/src/qemu/qemu_process.c
6d3351
index 70b06a28f..2e0f859ce 100644
6d3351
--- a/src/qemu/qemu_process.c
6d3351
+++ b/src/qemu/qemu_process.c
6d3351
@@ -3077,6 +3077,7 @@ qemuProcessRecoverMigrationOut(virQEMUDriverPtr driver,
6d3351
         }
6d3351
     }
6d3351
 
6d3351
+    qemuMigrationResetTLS(driver, vm, QEMU_ASYNC_JOB_NONE, NULL, NULL);
6d3351
     return 0;
6d3351
 }
6d3351
 
6d3351
-- 
6d3351
2.12.2
6d3351