Miklos Szeredi 26c3679101 fuse: destroy bdi on umount ... If a fuse filesystem is unmounted but the device file descriptor remains open and a new mount reuses the old device number, then the mount fails with EEXIST and the following warning is printed in the kernel log: WARNING: at fs/sysfs/dir.c:462 sysfs_add_one+0x35/0x3d() sysfs: duplicate filename '0:15' can not be created The cause is that the bdi belonging to the fuse filesystem was destoryed only after the device file was released. Fix this by calling bdi_destroy() from fuse_put_super() instead. Signed-off-by: Miklos Szeredi <mszeredi@suse.cz> CC: stable@kernel.org		2009-01-26 15:00:59 +01:00
..
control.c	fuse: style fixes	2008-11-26 12:03:54 +01:00
dev.c	fuse: destroy bdi on umount	2009-01-26 15:00:59 +01:00
dir.c	Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse	2009-01-06 17:01:20 -08:00
file.c	fuse: fix NULL deref in fuse_file_alloc()	2009-01-26 15:00:58 +01:00
fuse_i.h	fuse: add fuse_conn->release()	2008-11-26 12:03:56 +01:00
inode.c	fuse: destroy bdi on umount	2009-01-26 15:00:59 +01:00
Makefile	[PATCH] fuse: add control filesystem	2006-06-25 10:01:19 -07:00