Kevin Wolf 1b7f01d966 coroutine: Assert that no locks are held on termination ... A coroutine that takes a lock must also release it again. If the coroutine terminates without having released all its locks, it's buggy and we'll probably run into a deadlock sooner or later. Make sure that we don't get such cases. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>		2016-09-05 19:06:48 +02:00
..
acl.c
base64.c
bitmap.c
bitops.c
buffer.c
compatfd.c
coroutine-gthread.c
coroutine-sigaltstack.c
coroutine-ucontext.c
coroutine-win32.c
crc32c.c
cutils.c
envlist.c
error.c
event_notifier-posix.c
event_notifier-win32.c
fifo8.c
getauxval.c
hbitmap.c
hexdump.c
host-utils.c
id.c
iov.c
log.c
Makefile.objs
memfd.c
mmap-alloc.c
module.c
notify.c
osdep.c
oslib-posix.c
oslib-win32.c
path.c
qdist.c
qemu-config.c
qemu-coroutine-io.c
qemu-coroutine-lock.c	coroutine: Assert that no locks are held on termination	2016-09-05 19:06:48 +02:00
qemu-coroutine-sleep.c
qemu-coroutine.c	coroutine: Assert that no locks are held on termination	2016-09-05 19:06:48 +02:00
qemu-error.c
qemu-openpty.c
qemu-option.c
qemu-progress.c
qemu-sockets.c
qemu-thread-posix.c
qemu-thread-win32.c
qemu-timer-common.c
qht.c
range.c
rcu.c
readline.c
rfifolock.c
throttle.c
timed-average.c
trace-events	trace-events: fix first line comment in trace-events	2016-08-12 10:36:01 +01:00
unicode.c
uri.c