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