qemu-e2k/hw/9pfs
Aneesh Kumar K.V 02cb7f3a25 hw/9pfs: Use read-write lock for protecting fid path.
On rename we take the write lock and this ensure path
doesn't change as we operate on them.

Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
2011-09-22 21:38:52 +05:30
..
codir.c hw/9pfs: Use read-write lock for protecting fid path. 2011-09-22 21:38:52 +05:30
cofile.c hw/9pfs: Use read-write lock for protecting fid path. 2011-09-22 21:38:52 +05:30
cofs.c hw/9pfs: Use read-write lock for protecting fid path. 2011-09-22 21:38:52 +05:30
coxattr.c hw/9pfs: Use read-write lock for protecting fid path. 2011-09-22 21:38:52 +05:30
virtio-9p-coth.c Don't use g_thread_get_initialized. 2011-09-09 12:58:16 -05:00
virtio-9p-coth.h hw/9pfs: Use read-write lock for protecting fid path. 2011-09-22 21:38:52 +05:30
virtio-9p-debug.c virtio-9p: Fix syntax error in debug code 2011-09-09 09:51:07 +01:00
virtio-9p-debug.h
virtio-9p-device.c hw/9pfs: Use read-write lock for protecting fid path. 2011-09-22 21:38:52 +05:30
virtio-9p-local.c use readdir_r instead of readdir for reentrancy 2011-08-22 09:44:52 +05:30
virtio-9p-posix-acl.c
virtio-9p-xattr-user.c
virtio-9p-xattr.c Use glib memory allocation and free functions 2011-08-20 23:01:08 -05:00
virtio-9p-xattr.h
virtio-9p.c hw/9pfs: Use read-write lock for protecting fid path. 2011-09-22 21:38:52 +05:30
virtio-9p.h hw/9pfs: Use read-write lock for protecting fid path. 2011-09-22 21:38:52 +05:30