Re: [REGRESSION] bisected: 3.8 -> 3.9 cannot umount after using fuse

On Sat, May 04, 2013 at 08:02:40PM +0200, Michael Leun wrote: > On Sat, 4 May 2013 16:52:14 +0100 > Al Viro wrote: > > > On Sat, May 04, 2013 at 12:45:19PM +0200, Michael Leun wrote: > > > > > After reverting 57eccb830f1cc93d4b506ba306d8dfa685e0c88f from 3.9 > > > that umount above works (not bu

Re: [REGRESSION] bisected: 3.8 -> 3.9 cannot umount after using fuse

On Sat, 4 May 2013 16:52:14 +0100 Al Viro wrote: > On Sat, May 04, 2013 at 12:45:19PM +0200, Michael Leun wrote: > > > After reverting 57eccb830f1cc93d4b506ba306d8dfa685e0c88f from 3.9 > > that umount above works (not busy). > > Sigh... Check if the following fix works for your testcase: > dif

Re: [REGRESSION] bisected: 3.8 -> 3.9 cannot umount after using fuse

On Sat, May 04, 2013 at 12:45:19PM +0200, Michael Leun wrote: > After reverting 57eccb830f1cc93d4b506ba306d8dfa685e0c88f from 3.9 that > umount above works (not busy). Sigh... Check if the following fix works for your testcase: diff --git a/fs/namespace.c b/fs/namespace.c index b4f96a5..b68eef2d

[REGRESSION] bisected: 3.8 -> 3.9 cannot umount after using fuse

Mount some filesystem, below that mountpoint as user mount some fuse fs (tried that with sshfs and fuseiso, both same error), fusermount -u the fuse fs, try to unmount the filesystem -> busy. ml@lara:~> id -u 500 ml@lara:~> grep test /etc/fstab /dev/vg1/test /mnt2 ext4acl,user_xattr,user,noauto