linux/fs/fuse
Miklos Szeredi c47752673a fuse: don't hold lock over request_wait_answer()
Only hold fc->lock over sections of request_wait_answer() that actually
need it.  If wait_event_interruptible() returns zero, it means that the
request finished.  Need to add memory barriers, though, to make sure that
all relevant data in the request is synchronized.

Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
2015-07-01 16:26:00 +02:00
..
control.c VFS: normal filesystems (and lustre): d_inode() annotations 2015-04-15 15:06:57 -04:00
cuse.c make new_sync_{read,write}() static 2015-04-11 22:29:40 -04:00
dev.c fuse: don't hold lock over request_wait_answer() 2015-07-01 16:26:00 +02:00
dir.c VFS: normal filesystems (and lustre): d_inode() annotations 2015-04-15 15:06:57 -04:00
file.c fuse: req use bitops 2015-07-01 16:25:58 +02:00
fuse_i.h fuse: use per req lock for lock/unlock_request() 2015-07-01 16:25:58 +02:00
inode.c fuse: simplify unique ctr 2015-07-01 16:26:00 +02:00
Kconfig fuse: Move CUSE Kconfig entry from fs/Kconfig into fs/fuse/Kconfig 2013-01-17 13:08:45 +01:00
Makefile CUSE: implement CUSE - Character device in Userspace 2009-06-09 11:24:11 +02:00