fs/unionfs/copyup.c  |    9 ++++++-
 fs/unionfs/lookup.c  |   64 +++++++++++++++++++++++++++++++++++++++++++++++++-
 fs/unionfs/rdstate.c |    2 +-
 fs/unionfs/rename.c  |    9 ++++++-
 fs/unionfs/subr.c    |   18 ++++++++++++-
 fs/unionfs/super.c   |    2 +-
 fs/unionfs/union.h   |    2 +
 7 files changed, 99 insertions(+), 7 deletions(-)

New commits:
commit 65f0037950d1b006a2a46f830753f77f431b0784
Author: Erez_Zadok <[EMAIL PROTECTED]>
Date:   Mon Jul 23 03:13:01 2007 -0400

    Unionfs: pass nameidata intent information to lower level file systems
    
    As of 2.6.23-rc1, nfs2 and nfs3, like nfs4 before them, begin relying on the
    struct nameidata and especially the intent information, which is passed to
    vfs_create() and others.  So, as of now, unionfs properly creates and passes
    that intent data to the lower level file system.  Currently supported are
    LOOKUP_CREATE open intents.  Others can be supported in the future
    incrementally.
    
    Signed-off-by: Erez Zadok <[EMAIL PROTECTED]>

commit 12ab1209a7fed65bff471c72334a5060fe18b152
Author: Erez_Zadok <[EMAIL PROTECTED]>
Date:   Sun Jul 22 21:53:49 2007 -0400

    Unionfs: kmem_cache_create doesn't take a dtor argument any longer
    
    Porting unionfs to 2.6.23-rc1
    
    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

Reply via email to