fs/unionfs/Makefile | 2 +- fs/unionfs/compat.h | 3 +++ fs/unionfs/inode.c | 30 +++++++++++++++++++++++++----- fs/unionfs/union.h | 9 +++++++++ 4 files changed, 38 insertions(+), 6 deletions(-)
New commits: commit 0244b5c528cc24218bc64e16ffb68191f958eb55 Author: Erez Zadok <[email protected]> Date: Tue Sep 22 17:55:42 2009 -0400 Unionfs: Release 2.5.3 Signed-off-by: Erez Zadok <[email protected]> commit fb00874393f0ed501d7a3cb78e32342f3fa5b268 Author: Erez Zadok <[email protected]> Date: Tue Sep 22 17:45:57 2009 -0400 Unionfs: handle an open-unlink-ftruncate sequence If someone calls open(), then unlink(), then ftruncate() on a file (rare, but possible), then it's possible for unionfs to get an unlinked inode which doesn't have an inode->i_sb and its inode->i_ino is zero. Don't oops in that case. Signed-off-by: Erez Zadok <[email protected]> commit db5f65c7e045c0ef960c14a6fb3feb973b7ff001 Author: Erez Zadok <[email protected]> Date: Tue Sep 22 17:44:09 2009 -0400 Unionfs: fix readonly nfs2/3 permission handling In unionfs_permission: NFSv2/3 return EACCES on readonly-exported, locally readonly-mounted file systems, instead of EROFS like other file systems do. So we have no choice here but to intercept this and ignore it for NFS branches marked readonly. Specifically, we avoid using NFS's own "broken" ->permission method, and rely on generic_permission() to do basic checking for us. Signed-off-by: Erez Zadok <[email protected]> _______________________________________________ unionfs-cvs mailing list: http://unionfs.filesystems.org/ [email protected] http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs-cvs
