linux-kernel.vger.kernel.org archive mirror
 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 update for 5.7
Date: Wed, 8 Apr 2020 10:54:23 +0200	[thread overview]
Message-ID: <20200408085423.GA21974@miu.piliscsaba.redhat.com> (raw)

Hi Linus,

Please pull from:

  git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git tags/ovl-update-5.7

 - Fix failure to copy-up files from certain NFSv4 mounts.

 - Sort out inconsistencies between st_ino and i_ino (used in /proc/locks).

 - Allow consistent (POSIX-y) inode numbering in more cases.

 - Allow virtiofs to be used as upper layer.

 - Miscellaneous cleanups and fixes.

Thanks,
Miklos

---
Al Viro (1):
      ovl: ovl_obtain_alias(): don't call d_instantiate_anon() for old

Amir Goldstein (10):
      ovl: fix value of i_ino for lower hardlink corner case
      ovl: fix out of date comment and unreachable code
      ovl: factor out helper ovl_get_root()
      ovl: simplify i_ino initialization
      ovl: check if upper fs supports RENAME_WHITEOUT
      ovl: strict upper fs requirements for remote upper fs
      ovl: use a private non-persistent ino pool
      ovl: avoid possible inode number collisions with xino=on
      ovl: enable xino automatically in more cases
      ovl: document xino expected behavior

Chengguang Xu (1):
      ovl: fix a typo in comment

Gustavo A. R. Silva (1):
      ovl: replace zero-length array with flexible-array member

Miklos Szeredi (7):
      ovl: document permission model
      ovl: ignore failure to copy up unknown xattrs
      ovl: restructure dentry revalidation
      ovl: separate detection of remote upper layer from stacked overlay
      ovl: decide if revalidate needed on a per-dentry basis
      ovl: allow remote upper
      ovl: fix WARN_ON nlink drop to zero

---
 Documentation/filesystems/overlayfs.rst |  82 +++++++++-
 fs/overlayfs/copy_up.c                  |  16 +-
 fs/overlayfs/dir.c                      |  31 +++-
 fs/overlayfs/export.c                   |  40 ++---
 fs/overlayfs/inode.c                    |  99 ++++++++----
 fs/overlayfs/namei.c                    |   5 +-
 fs/overlayfs/overlayfs.h                |  25 +++-
 fs/overlayfs/ovl_entry.h                |   2 +
 fs/overlayfs/readdir.c                  |  25 +++-
 fs/overlayfs/super.c                    | 258 ++++++++++++++++++++++----------
 fs/overlayfs/util.c                     |  40 +++--
 11 files changed, 460 insertions(+), 163 deletions(-)

             reply	other threads:[~2020-04-08  8:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08  8:54 Miklos Szeredi [this message]
2020-04-09  4:55 ` [GIT PULL] overlayfs update for 5.7 pr-tracker-bot

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=20200408085423.GA21974@miu.piliscsaba.redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).