Prev: [PATCH 07/38] whiteout: Set opaque flag if new directory was previously a whiteout
Next: [PATCH 13/38] fallthru: Basic fallthru definitions
From: Valerie Aurora on 6 Aug 2010 18:50 Major changes since last version: * Separate MS_FALLTHRU instead of piggybacking on MS_WHITEOUT * Renumbering of ext2 flags - backwards incompatible * Bug fix for > 2 layers * Better mount error messages (from Miklos Szeredi) * Rebase against 2.6.35 This branch is named "ms_fallthru" and is in the usual git tree: git://git.kernel.org/pub/scm/linux/kernel/git/val/linux-2.6.git You will have to update your util-linux-ng and e2fsprogs to get the new magic numbers for ext2 feature flags and mount options. You have to throw away any existing union mount ext2 disk images and build new ones (all two of you who have them). Branch "union_mount" of both: git://git.kernel.org/pub/scm/fs/ext2/val/e2fsprogs.git git://git.kernel.org/pub/scm/utils/util-linux-ng/val/util-linux-ng.git -VAL Felix Fietkau (2): whiteout: jffs2 whiteout support fallthru: jffs2 fallthru support Jan Blunck (10): VFS: Make lookup_hash() return a struct path autofs4: Save autofs trigger's vfsmount in super block info whiteout/NFSD: Don't return information about whiteouts to userspace whiteout: Add vfs_whiteout() and whiteout inode operation whiteout: Set opaque flag if new directory was previously a whiteout whiteout: Allow removal of a directory with whiteouts whiteout: Split of ext2_append_link() from ext2_add_link() whiteout: ext2 whiteout support union-mount: Introduce MNT_UNION and MS_UNION flags union-mount: Call do_whiteout() on unlink and rmdir in unions Valerie Aurora (26): VFS: Comment follow_mount() and friends VFS: Add read-only users count to superblock whiteout: tmpfs whiteout support fallthru: Basic fallthru definitions fallthru: ext2 fallthru support fallthru: tmpfs fallthru support union-mount: Union mounts documentation union-mount: Introduce union_dir structure and basic operations union-mount: Free union dirs on removal from dcache union-mount: Support for union mounting file systems union-mount: Implement union lookup union-mount: Copy up directory entries on first readdir() VFS: Split inode_permission() and create path_permission() VFS: Create user_path_nd() to lookup both parent and target union-mount: In-kernel file copyup routines union-mount: Implement union-aware access()/faccessat() union-mount: Implement union-aware link() union-mount: Implement union-aware rename() union-mount: Implement union-aware writable open() union-mount: Implement union-aware chown() union-mount: Implement union-aware truncate() union-mount: Implement union-aware chmod()/fchmodat() union-mount: Implement union-aware lchown() union-mount: Implement union-aware utimensat() union-mount: Implement union-aware setxattr() union-mount: Implement union-aware lsetxattr() Documentation/filesystems/union-mounts.txt | 752 +++++++++++++++++++++++++++ Documentation/filesystems/vfs.txt | 16 +- fs/Kconfig | 13 + fs/Makefile | 1 + fs/autofs4/autofs_i.h | 1 + fs/autofs4/init.c | 11 +- fs/autofs4/root.c | 6 + fs/compat.c | 9 + fs/dcache.c | 32 ++- fs/ext2/dir.c | 248 +++++++++- fs/ext2/ext2.h | 4 + fs/ext2/inode.c | 11 +- fs/ext2/namei.c | 85 +++- fs/ext2/super.c | 7 + fs/jffs2/dir.c | 104 ++++- fs/jffs2/fs.c | 4 + fs/jffs2/super.c | 2 +- fs/libfs.c | 21 +- fs/namei.c | 754 ++++++++++++++++++++++++---- fs/namespace.c | 289 +++++++++++- fs/nfsd/nfs3xdr.c | 5 + fs/nfsd/nfs4xdr.c | 5 + fs/nfsd/nfsxdr.c | 4 + fs/open.c | 116 ++++- fs/readdir.c | 18 + fs/super.c | 24 + fs/union.c | 699 ++++++++++++++++++++++++++ fs/union.h | 80 +++ fs/utimes.c | 14 +- fs/xattr.c | 65 ++- include/linux/dcache.h | 19 +- include/linux/ext2_fs.h | 8 + include/linux/fs.h | 26 + include/linux/jffs2.h | 8 + include/linux/mount.h | 6 +- include/linux/namei.h | 2 + mm/shmem.c | 193 +++++++- 37 files changed, 3480 insertions(+), 182 deletions(-) create mode 100644 Documentation/filesystems/union-mounts.txt create mode 100644 fs/union.c create mode 100644 fs/union.h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |