On Fri, Apr 21, 2023 at 10:25 AM Michal Privoznik <mprivozn@xxxxxxxxxx> wrote:
There's a comment in testQemuHotplug() trying to explain why we
need to unlock the monitor object. Well, while it might have been
correct when being introduced, it's no long factually correct as
*no longer
just any function (attach/detach/update) might talk to the
monitor and it expects the monitor to be unlocked (as it calls
qemuDomainObjEnterMonitor() + qemuDomainObjExitMonitor()).
Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>
---
tests/qemuhotplugtest.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
