"Richard W.M. Jones" <rjones@xxxxxxxxxx> writes: > On Wed, May 13, 2015 at 10:27:09AM +0200, Miklos Szeredi wrote: >> [CCs added] >> >> On Tue, May 12, 2015 at 11:34 AM, Richard W.M. Jones <rjones@xxxxxxxxxx> wrote: >> > >> > Has something changed in FUSE / the kernel in the past few months so >> > that 'fusermount -u /mp' reports the error: >> > >> > fusermount: failed to unmount /mp: Device or resource busy >> > >> >> That's from the umount2() syscall, and most likely not a fuse issue. >> >> > and returns a non-zero exit code, but the mountpoint is unmounted >> > anyway? >> >> Is this in 4.1-rc? If so, then the recent fs/namespace.c patches from >> Eric Biederman would be suspect. > > Yes, this is reproducible with: > > kernel-4.1.0-0.rc2.git3.1.fc23.x86_64 (from Fedora Rawide) > fuse-2.9.3-4.fc22.x86_64 > > I will see if I can make a small reproducer and get back. I will be happy to look at this if there is a reasonably small reproducer. I don't think I changed anything that could cause that kind of failure, but I have touched a fair amount of that code recently and at the very least I will be familiar with it. The only case I can imagine is the mount point being deleted. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
