Public bug reported: In kernel v5.9+ there was a refactor to the unmount code path that results in libfuse no longer being able to detect UMOUNT_NOFOLLOW. This resulted in an alternate code path that relied on being able to call unshare and some other work.
The patch that caused the bug upstream: https://lore.kernel.org/linux-fsdevel/20200726071356.287160-3-...@lst.de/ The fix upstream (not in tree): https://lore.kernel.org/linux-fsdevel/20201223102604.2078-1-sar...@sargun.me/ The fix in libfuse: https://github.com/libfuse/libfuse/commit/b96e4758041ffac1b8d8c39f4897edd6182a46e9 ** Affects: fuse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909502 Title: FUSE fails to unmount without privilege in kernel v5.9+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1909502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
