Miklos Szeredi baebccbe99 fuse: hold inode instead of path after release ... path_put() in release could trigger a DESTROY request in fuseblk. The possible deadlock was worked around by doing the path_put() with schedule_work(). This complexity isn't needed if we just hold the inode instead of the path. Since we now flush all requests before destroying the super block we can be sure that all held inodes will be dropped. Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>		2014-12-12 09:49:04 +01:00
..
control.c	fuse: add __exit to fuse_ctl_cleanup	2014-04-28 14:19:21 +02:00
cuse.c	fuse: flush requests on umount	2014-12-12 09:49:04 +01:00
dev.c	Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse	2014-07-15 08:57:17 -07:00
dir.c	vfs: Make d_invalidate return void	2014-10-09 02:38:57 -04:00
file.c	fuse: hold inode instead of path after release	2014-12-12 09:49:04 +01:00
fuse_i.h	fuse: hold inode instead of path after release	2014-12-12 09:49:04 +01:00
inode.c	fuse: flush requests on umount	2014-12-12 09:49:04 +01: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