fs/unionfs/Makefile | 2 +- fs/unionfs/inode.c | 30 +++++++++++++++++++++++++----- fs/unionfs/union.h | 9 +++++++++ 3 files changed, 35 insertions(+), 6 deletions(-)
New commits: commit 622b472d13093a81ff1d6fa0ea2cd3354ad99da2 Author: Erez Zadok <[email protected]> Date: Tue Sep 22 17:55:08 2009 -0400 Unionfs: Release 2.5.3 Signed-off-by: Erez Zadok <[email protected]> commit c0b4548d2c0ec2a7ad7de6d4cc6ff11d78a43ff1 Author: Erez Zadok <[email protected]> Date: Tue Sep 22 17:46:00 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 311062f95b6c07f337ce71fce4a83c837bfbaffc Author: Erez Zadok <[email protected]> Date: Tue Sep 22 17:34:11 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
