linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [GIT PULL] multi-layer support for overlay filesystem
Date: Wed, 18 Feb 2015 11:59:03 +0100	[thread overview]
Message-ID: <20150218105903.GA5986@tucsk.suse.de> (raw)
In-Reply-To: <20150211093039.GA6817@tucsk.suse.de>

On Wed, Feb 11, 2015 at 10:30:39AM +0100, Miklos Szeredi wrote:
> Al,
> 
> Please pull from
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-next
> 
> This adds support for multiple read-only layers to overlayfs.  It also makes the
> writable upper layer optional.
> 
> This is a highly requested feature and has been in -next for the last cycle.

Ping.

Not sure whom I should send overlayfs pull requests to.  Would direct to Linus
be better?

Thanks,
Miklos


> ---
> Miklos Szeredi (16):
>       ovl: check whiteout while reading directory
>       ovl: make path-type a bitmap
>       ovl: dont replace opaque dir
>       ovl: add mutli-layer infrastructure
>       ovl: helper to iterate layers
>       ovl: multi-layer readdir
>       ovl: multi-layer lookup
>       ovl: check whiteout on lowest layer as well
>       ovl: lookup ENAMETOOLONG on lower means ENOENT
>       ovl: allow statfs if no upper layer
>       ovl: mount: change order of initialization
>       ovl: improve mount helpers
>       ovl: make upperdir optional
>       ovl: support multiple lower layers
>       ovl: add testsuite to docs
>       ovl: document lower layer ordering
> 
> Seunghun Lee (1):
>       ovl: Prevent rw remount when it should be ro mount
> 
> hujianyang (5):
>       ovl: Cleanup redundant blank lines
>       ovl: Use macros to present ovl_xattr
>       ovl: Fix kernel panic while mounting overlayfs
>       ovl: Fix opaque regression in ovl_lookup
>       ovl: discard independent cursor in readdir()
> 
> ---
>  Documentation/filesystems/overlayfs.txt |  28 ++
>  fs/overlayfs/copy_up.c                  |   5 +-
>  fs/overlayfs/dir.c                      |  28 +-
>  fs/overlayfs/inode.c                    |  12 +-
>  fs/overlayfs/overlayfs.h                |  18 +-
>  fs/overlayfs/readdir.c                  | 181 +++++-----
>  fs/overlayfs/super.c                    | 564 +++++++++++++++++++++-----------
>  7 files changed, 517 insertions(+), 319 deletions(-)

  reply	other threads:[~2015-02-18 10:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11  9:30 [GIT PULL] multi-layer support for overlay filesystem Miklos Szeredi
2015-02-18 10:59 ` Miklos Szeredi [this message]
2015-02-19  7:42   ` Al Viro
  -- strict thread matches above, loose matches on Subject: below --
2014-12-09 10:37 Miklos Szeredi
2014-12-12  9:47 ` Al Viro
2014-12-13  0:07   ` Miklos Szeredi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150218105903.GA5986@tucsk.suse.de \
    --to=miklos@szeredi.hu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@ZenIV.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).