Linux filesystem development
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-unionfs@vger.kernel.org
Subject: [GIT PULL] overlayfs fixes for 4.5-rc7
Date: Mon, 7 Mar 2016 09:49:33 +0100	[thread overview]
Message-ID: <20160307084933.GB8655@tucsk> (raw)

Hi Linus,

Please pull from:

  git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-linus

This contains overlayfs bug fixes.  All marked as -stable material.

Thanks,
Miklos

---
Konstantin Khlebnikov (3):
      ovl: fix working on distributed fs as lower layer
      ovl: ignore lower entries when checking purity of non-directory entries
      ovl: copy new uid/gid into overlayfs runtime inode

Rui Wang (1):
      ovl: fix getcwd() failure after unsuccessful rmdir

---
 fs/overlayfs/dir.c   | 10 +++++++++-
 fs/overlayfs/inode.c |  2 ++
 fs/overlayfs/super.c | 13 ++++++++-----
 3 files changed, 19 insertions(+), 6 deletions(-)

                 reply	other threads:[~2016-03-07  8:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160307084933.GB8655@tucsk \
    --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 \
    /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