We are pleased to announce Unionfs 2.5. This is a major new release.
Although we usually urge caution before using a major release, in this case
we believe it is safe to upgrade to 2.5 (esp. if you've had problems with
previous releases).
This release includes several major race fixes, as well as several other
smaller fixes:
1. Audited the locking scheme and reworked it to address several comments
from LKML code reviews.
2. Also based on LKML reviews, now using get_parent whenever needed.
These two changes resulted in fixing several lingering races (especially
interactions of rename and other ops), as well as cleaned up much of the
dentry revalidation code. Also of note are continuing efforts to convert
the code to use struct path's whenever possible (while trying not to break
anything else :-)
Below is a list of smaller changes in this release, most of them based on
user reports.
- bugfix: avoid infinite loop in unionfs_file_revalidate
(instead, return ESTALE and let the VFS handle it)
- bugfix: don't fail in ->release (this VFS method must succeed)
- bugfix: if ->setattr fails, return EINVAL (not BUG_ON)
- bugfix: don't leave inodes behind (only for 2.6.18.x)
- bugfix: don't forget to dput last lower dentry in ->mkdir
- bugfix: don't try to open unhashed dentries in ->open (return ENOENT)
- bugfix: don't BUG_ON in lookup_full if can't find mnt
- bugfix: set the mnt in ->unlink (prevent oops in "rm -fr")
- bugfix: prevent privilege escalation during copyup
- if ->put_super detects possible leaks, just WARN_ON (not BUG_ON)
- began removing references to unused nameidata structures (which'll mostly
go away from the VFS eventually)
- assorted code cleanups thanks to the locking rework
- updated for 2.6.25.17, 2.6.26.5, and 2.6.27-rc6.
This code was tested on all of our ports: 2.6.{26,25,24,23,22,21,20,19,18,9}
as well as -mm and 2.6.27-rc6. You can find links to specific releases for
specific kernels in either of these URLs:
<http://unionfs.filesystems.org/>
<http://download.filesystems.org/unionfs/unionfs-2.x/>
As usual, feel free to report all problems you find to
<https://bugzilla.filesystems.org/>
Enjoy.
Erez, on behalf of the Unionfs team.
_______________________________________________
unionfs mailing list: http://unionfs.filesystems.org/
unionfs@mail.fsl.cs.sunysb.edu
http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
