diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2018-12-28 14:40:41 +0100 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2019-02-05 16:50:18 +0100 |
| commit | 82e870bac441f231deb72b64c9baf2f2fbd5bdbb (patch) | |
| tree | 222eef2927695d383133546f3ee2b4165ea263b5 /cpus-common.c | |
| parent | 1b9d35f33c85e63377b02eba276dd1bb102247f9 (diff) | |
monitor: do not use QTAILQ_FOREACH_SAFE across critical sections
monitor_qmp_requests_pop_any_with_lock cannot modify the monitor list
concurrently with monitor_cleanup, since the dispatch bottom half
runs in the main thread, but anyway it is a bit ugly to keep
"next" live across critical sections of monitor_lock and Coverity
complains (CID 1397072).
Replace QTAILQ_FOREACH_SAFE with a while loop and QTAILQ_FIRST,
it is cleaner and more future-proof.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'cpus-common.c')
0 files changed, 0 insertions, 0 deletions