chr_write_lock was introduced in commit 9005b2a7589540a3733b3abdcfbccfe7746cd1a1
but was used uninitialized. It caused segmentation fault on windows hosts.
Add missing lock initialization to qemu_chr_alloc.
Cc: Paolo Bonzini <pbonz...@redhat.com>
Cc: Luiz Capitulino <lcapitul...@redhat.com>
Cc: Fam Zheng <f...@redhat.com>
Signed-off-by: Kirill Batuzov <batuz...@ispras.ru>
Signed-off-by: Nikita Belov <zod...@ispras.ru>
---
qemu-char.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/qemu-char.c b/qemu-char.c
index 2e50a10..17bd360 100644
--- a/qemu-char.c
+++ b/qemu-char.c
@@ -94,6 +94,7 @@ static QTAILQ_HEAD(CharDriverStateHead, CharDriverState)
chardevs =
CharDriverState *qemu_chr_alloc(void)
{
CharDriverState *chr = g_malloc0(sizeof(CharDriverState));
+ qemu_mutex_init(&chr->chr_write_lock);
return chr;
}
--
1.7.10.4
