linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-unionfs@vger.kernel.org
Subject: Re: [GIT PULL] overlay filesystem fixes for 3.18
Date: Fri, 21 Nov 2014 11:43:56 +0100	[thread overview]
Message-ID: <CA+icZUVSdSDqUCf3+2SmGx4DfhKvxPi4ivvhNzTEnbe1j4eFQA@mail.gmail.com> (raw)
In-Reply-To: <20141120164531.GB3596@tucsk>

On Thu, Nov 20, 2014 at 5:45 PM, Miklos Szeredi <miklos@szeredi.hu> wrote:
> Hi Al,
>
> Please pull from
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-current
>

This seems to be the place where overlayfs-fixes are collected for a
git-pull request.
Can you add a "T:" line with the Git tree into MAINTAINERS file if
this is the case?
If not please let the people know about current situation.
Thanks.

- Sedat -

> The biggest change is to rename the filesystem from "overlayfs" to "overlay".
> This will allow legacy overlayfs to be easily carried by distros alongside the
> new mainline one.  Also fix a couple of copy-up races and allow escaping comma
> character in filenames.
>
> Thanks,
> Miklos
>
> ---
> Miklos Szeredi (8):
>       ovl: rename filesystem type to "overlay"
>       ovl: fix remove/copy-up race
>       ovl: fix race in private xattr checks
>       ovl: allow filenames with comma
>       ovl: use lockless_dereference() for upperdentry
>       ovl: pass dentry into ovl_dir_read_merged()
>       ovl: update MAINTAINERS
>       ovl: ovl_dir_fsync() cleanup
>
> ---
>  Documentation/filesystems/overlayfs.txt |  2 +-
>  MAINTAINERS                             |  7 ++--
>  fs/Makefile                             |  2 +-
>  fs/overlayfs/Kconfig                    |  2 +-
>  fs/overlayfs/Makefile                   |  4 +--
>  fs/overlayfs/dir.c                      | 31 ++++++++++-------
>  fs/overlayfs/inode.c                    | 27 ++++++++++-----
>  fs/overlayfs/readdir.c                  | 39 +++++++++------------
>  fs/overlayfs/super.c                    | 61 ++++++++++++++++++++++++++-------
>  9 files changed, 111 insertions(+), 64 deletions(-)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-11-21 10:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 16:45 [GIT PULL] overlay filesystem fixes for 3.18 Miklos Szeredi
2014-11-20 21:00 ` Al Viro
2014-11-21 10:43 ` Sedat Dilek [this message]
2014-11-21 10:50   ` Miklos Szeredi
2014-11-22  8:40     ` Sedat Dilek
2014-11-21 11:32 ` Hans-Peter Jansen
2014-11-21 12:41   ` Miklos Szeredi
2014-11-21 14:51     ` Hans-Peter Jansen

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=CA+icZUVSdSDqUCf3+2SmGx4DfhKvxPi4ivvhNzTEnbe1j4eFQA@mail.gmail.com \
    --to=sedat.dilek@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --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).