On Mon, Sep 29, 2014 at 4:14 PM, Miklos Szeredi <mik...@szeredi.hu> wrote:
> I'd like to propose overlayfs for inclusion into 3.18.
>
> Al, would you mind giving it a review?
>
> Git tree is here:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git 
> overlayfs.current
>

Nice to see that the overlayfs "dream" comes true.
overlayfs.current has now got a "review" - will there be a v25
pull-request soonish or is overlayfs.current still in WIP?
Where is that review process happening? On linux-fsdevel I could not
find any informations.

Some updated patches have no review credits - for example the big
overlay filesystem patch which mentions AV's review, etc.

Maintainers file could have a tree item pointing to your personal Git
repository.

Is the documentation up2date?

Some files below fs/overlayfs/ have copyright pointing to year 2011 by
Novell - needs an update?

Thought about a co-maintainer?

Docs could have a pointer to the testsuite by David Howells [1]?

...etc.

- Sedat -

[1] http://git.infradead.org/users/dhowells/unionmount-testsuite.git

> Thanks,
> Miklos
>
> ---
> Andy Whitcroft (1):
>       overlayfs: add statfs support
>
> Erez Zadok (1):
>       overlayfs: implement show_options
>
> Miklos Szeredi (11):
>       vfs: add i_op->dentry_open()
>       vfs: export do_splice_direct() to modules
>       vfs: export __inode_permission() to modules
>       vfs: introduce clone_private_mount()
>       vfs: export check_sticky()
>       vfs: add whiteout support
>       vfs: add RENAME_WHITEOUT
>       ext4: support RENAME_WHITEOUT
>       shmem: support RENAME_WHITEOUT
>       overlay filesystem
>       fs: limit filesystem stacking depth
>
> Neil Brown (1):
>       overlay: overlay filesystem documentation
>
> Sedat Dilek (1):
>       vfs: dcache: Export d_ancestor to modules
>
> ---
>  Documentation/filesystems/Locking       |   2 +
>  Documentation/filesystems/overlayfs.txt | 198 +++++++
>  Documentation/filesystems/vfs.txt       |   7 +
>  MAINTAINERS                             |   7 +
>  fs/Kconfig                              |   1 +
>  fs/Makefile                             |   1 +
>  fs/btrfs/ioctl.c                        |  20 +-
>  fs/dcache.c                             |   1 +
>  fs/ecryptfs/main.c                      |   7 +
>  fs/ext4/namei.c                         |  95 +++-
>  fs/internal.h                           |   7 -
>  fs/namei.c                              |  41 +-
>  fs/namespace.c                          |  27 +
>  fs/open.c                               |  23 +-
>  fs/overlayfs/Kconfig                    |  10 +
>  fs/overlayfs/Makefile                   |   7 +
>  fs/overlayfs/copy_up.c                  | 431 +++++++++++++++
>  fs/overlayfs/dir.c                      | 914 
> ++++++++++++++++++++++++++++++++
>  fs/overlayfs/inode.c                    | 408 ++++++++++++++
>  fs/overlayfs/overlayfs.h                | 187 +++++++
>  fs/overlayfs/readdir.c                  | 518 ++++++++++++++++++
>  fs/overlayfs/super.c                    | 762 ++++++++++++++++++++++++++
>  fs/splice.c                             |   1 +
>  include/linux/fs.h                      |  37 ++
>  include/linux/mount.h                   |   3 +
>  include/uapi/linux/fs.h                 |   1 +
>  mm/shmem.c                              |  36 +-
>  27 files changed, 3694 insertions(+), 58 deletions(-)
>  create mode 100644 Documentation/filesystems/overlayfs.txt
>  create mode 100644 fs/overlayfs/Kconfig
>  create mode 100644 fs/overlayfs/Makefile
>  create mode 100644 fs/overlayfs/copy_up.c
>  create mode 100644 fs/overlayfs/dir.c
>  create mode 100644 fs/overlayfs/inode.c
>  create mode 100644 fs/overlayfs/overlayfs.h
>  create mode 100644 fs/overlayfs/readdir.c
>  create mode 100644 fs/overlayfs/super.c
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to