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