monitor: guard iothread access by mon->use_io_thread
monitor_resume() and monitor_suspend() both want to "kick" the I/O thread if it is there, but in monitor_suspend() lacked the use_io_thread flag condition. This is required when we later only spawn the thread on first use. Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com> Reviewed-by: Eric Blake <eblake@redhat.com> Reviewed-by: Peter Xu <peterx@redhat.com> Message-Id: <20180925081507.11873-2-w.bumiller@proxmox.com> Signed-off-by: Markus Armbruster <armbru@redhat.com>
This commit is contained in:
parent
0ca70f19c0
commit
9a3e52e346
|
@ -4292,7 +4292,7 @@ int monitor_suspend(Monitor *mon)
|
||||||
|
|
||||||
atomic_inc(&mon->suspend_cnt);
|
atomic_inc(&mon->suspend_cnt);
|
||||||
|
|
||||||
if (monitor_is_qmp(mon)) {
|
if (monitor_is_qmp(mon) && mon->use_io_thread) {
|
||||||
/*
|
/*
|
||||||
* Kick I/O thread to make sure this takes effect. It'll be
|
* Kick I/O thread to make sure this takes effect. It'll be
|
||||||
* evaluated again in prepare() of the watch object.
|
* evaluated again in prepare() of the watch object.
|
||||||
|
|
Loading…
Reference in New Issue