Comment 5 for bug 634554

Revision history for this message
Colin Watson (cjwatson) wrote : Re: please package libfuse2 > 2.8.3

On second thoughts, I think the easiest fix for Maverick will in fact be a merge from Debian, despite the relatively late stage in the release. Here's the complete upstream changelog between 2.8.1 and 2.8.4:

2010-04-26 Miklos Szeredi <email address hidden>

       * Released 2.8.4

2010-04-26 Miklos Szeredi <email address hidden>

       * Fix checking for symlinks in umount from /tmp. Reported by Al
       Viro

       * Fix umounting if /tmp is a symlink. Reported by Franco Broi

2010-02-18 Miklos Szeredi <email address hidden>

       * Fix definition of FUSE_OPT_END for C++. Reported by Tim
       Bruylants

2010-02-03 Miklos Szeredi <email address hidden>

       * Fix stack alignment for clone()

2010-02-01 Miklos Szeredi <email address hidden>

       * Released 2.8.3

2010-02-01 Miklos Szeredi <email address hidden>

       * Using "--no-canonicalize" with umount(8) conflicts with the race
       fix, sinceit assumes the supplied path is absolute, while the race
       fix relies on the path being relative to the current directory.
       Reported by Tom Rindborg

2010-01-26 Miklos Szeredi <email address hidden>

       * Released 2.8.2

2010-01-21 Miklos Szeredi <email address hidden>

       * Fix race if two "fusermount -u" instances are run in parallel.
       Reported by Dan Rosenberg

       * Make sure that the path to be unmounted doesn't refer to a
       symlink

2010-01-14 Miklos Szeredi <email address hidden>

       * Fix compile error on FreeBSD. Patch by Jay Sullivan

2009-12-17 Miklos Szeredi <email address hidden>

       * Use '--no-canonicalize' option of mount(8) (available in
       util-linux-ng version 2.17 or greater) to avoid calling
       readling(2) on the newly mounted filesystem before the mount
       procedure is finished. This has caused a deadlock if "audit" was
       enabled in the kernel. Also use '--no-canonicalize' for umount to
       avoid touching the mounted filesystem.

I'm attaching a sanitised upstream diff, excluding changelogs and the autotools update. Note that we already had much of this as a security patch. It seems pretty straightforward to me, and the care taken to support legacy versions of mount should also ensure that it works properly in the initramfs.

(Lucid will be a different matter. A backport would be more appropriate there.)