[RFC,v2,20/26] replay: don't destroy mutex at exit

Message ID 20171114081824.27640.82263.stgit@pasha-VirtualBox
State New
Headers show
Series
  • replay additions
Related show

Commit Message

Pavel Dovgalyuk Nov. 14, 2017, 8:18 a.m.
Replay mutex is held by vCPU thread and destroy function is called
from atexit of the main thread. Therefore we cannot destroy it safely.

Signed-off-by: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>

---
 replay/replay.c |    1 -
 1 file changed, 1 deletion(-)

Comments

Paolo Bonzini Nov. 14, 2017, 1:36 p.m. | #1
On 14/11/2017 09:18, Pavel Dovgalyuk wrote:
> Replay mutex is held by vCPU thread and destroy function is called
> from atexit of the main thread. Therefore we cannot destroy it safely.
> 
> Signed-off-by: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>
> 
> ---
>  replay/replay.c |    1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/replay/replay.c b/replay/replay.c
> index 6e34b79..be1d4a2 100644
> --- a/replay/replay.c
> +++ b/replay/replay.c
> @@ -357,7 +357,6 @@ void replay_finish(void)
>      replay_snapshot = NULL;
>  
>      replay_finish_events();
> -    replay_mutex_destroy();
>  }
>  
>  void replay_add_blocker(Error *reason)
> 

Acked-by: Paolo Bonzini <pbonzini@redhat.com>

Patch

diff --git a/replay/replay.c b/replay/replay.c
index 6e34b79..be1d4a2 100644
--- a/replay/replay.c
+++ b/replay/replay.c
@@ -357,7 +357,6 @@  void replay_finish(void)
     replay_snapshot = NULL;
 
     replay_finish_events();
-    replay_mutex_destroy();
 }
 
 void replay_add_blocker(Error *reason)