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.19
Date: Mon, 30 May 2022 10:17:48 +0200	[thread overview]
Message-ID: <YpR9rJkjso7lXdFC@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.19

Support idmapped layers in overlayfs (Christian Brauner).  Add a fix to
exportfs that is relevant to open_by_handle_at(2) as well.  Also introduce
new lookup helpers that allow passing mnt_userns into inode_permission().

Thanks,
Miklos

---
Amir Goldstein (3):
      ovl: use wrappers to all vfs_*xattr() calls
      ovl: pass layer mnt to ovl_open_realfile()
      ovl: store lower path in ovl_inode

Christian Brauner (16):
      fs: add two trivial lookup helpers
      exportfs: support idmapped mounts
      ovl: pass ofs to creation operations
      ovl: add ovl_upper_mnt_userns() wrapper
      ovl: handle idmappings in creation operations
      ovl: pass ofs to setattr operations
      ovl: use ovl_do_notify_change() wrapper
      ovl: use ovl_lookup_upper() wrapper
      ovl: use ovl_path_getxattr() wrapper
      ovl: handle idmappings for layer fileattrs
      ovl: handle idmappings for layer lookup
      ovl: use ovl_copy_{real,upper}attr() wrappers
      ovl: handle idmappings in ovl_permission()
      ovl: handle idmappings in layer open helpers
      ovl: handle idmappings in ovl_xattr_{g,s}et()
      ovl: support idmapped layers

---
 fs/exportfs/expfs.c      |   5 +-
 fs/namei.c               |  70 ++++++++++++--
 fs/overlayfs/copy_up.c   |  90 +++++++++---------
 fs/overlayfs/dir.c       | 147 +++++++++++++++---------------
 fs/overlayfs/export.c    |   5 +
 fs/overlayfs/file.c      |  43 +++++----
 fs/overlayfs/inode.c     |  68 ++++++++------
 fs/overlayfs/namei.c     |  53 +++++++----
 fs/overlayfs/overlayfs.h | 232 +++++++++++++++++++++++++++++++++--------------
 fs/overlayfs/ovl_entry.h |   7 +-
 fs/overlayfs/readdir.c   |  48 +++++-----
 fs/overlayfs/super.c     |  57 ++++++------
 fs/overlayfs/util.c      | 103 ++++++++++++++++-----
 include/linux/namei.h    |   6 ++
 14 files changed, 598 insertions(+), 336 deletions(-)

             reply	other threads:[~2022-05-30  8:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30  8:17 Miklos Szeredi [this message]
2022-05-30 18:28 ` [GIT PULL] overlayfs update for 5.19 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=YpR9rJkjso7lXdFC@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).