All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	Christian Brauner <brauner@kernel.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-unionfs@vger.kernel.org
Subject: [GIT PULL] overlayfs update for 6.6
Date: Tue, 29 Aug 2023 13:35:12 +0300	[thread overview]
Message-ID: <20230829103512.2245736-1-amir73il@gmail.com> (raw)

Hi Linus,

This branch has been sitting in linux-next for several weeks and it
has gone through all the usual overlayfs test routines.

The branch has also been tested together with the changes in
Christain's vfs tree, which have been merged to master yesterday.

The branch merges cleanly with master branch of the moment.

Please refer to details about contained patch sets below.

Thanks,
Amir.

----------------------------------------------------------------

The following changes since commit 52a93d39b17dc7eb98b6aa3edb93943248e03b2f:

  Linux 6.5-rc5 (2023-08-06 15:07:51 -0700)

are available in the Git repository at:

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

for you to fetch changes up to adcd459ff805ce5e11956cfa1e9aa85471b6ae8d:

  ovl: validate superblock in OVL_FS() (2023-08-12 19:02:54 +0300)

----------------------------------------------------------------

Overlayfs update for 6.6

Contains the following patch sets:

Alexander Larsson added the verification feature needed by composefs
- [1] Add support for fs-verity checking of lowerdata

Amir Goldstein improved integration of overlayfs and fanotify
- [2] Report overlayfs file ids with fanotify

Andrea Righi fortified some overlayfs code
- [3] overlayfs: debugging check for valid superblock

[1] https://lore.kernel.org/r/cover.1687345663.git.alexl@redhat.com
[2] https://lore.kernel.org/r/20230713120344.1422468-1-amir73il@gmail.com
[3] https://lore.kernel.org/r/20230521082813.17025-1-andrea.righi@canonical.com

----------------------------------------------------------------
Alexander Larsson (4):
      ovl: Add framework for verity support
      ovl: Add versioned header for overlay.metacopy xattr
      ovl: Validate verity xattr when resolving lowerdata
      ovl: Handle verity during copy-up

Amir Goldstein (4):
      ovl: support encoding non-decodable file handles
      ovl: add support for unique fsid per instance
      ovl: store persistent uuid/fsid with uuid=on
      ovl: auto generate uuid for new overlay filesystems

Andrea Righi (3):
      ovl: Kconfig: introduce CONFIG_OVERLAY_FS_DEBUG
      ovl: make consistent use of OVL_FS()
      ovl: validate superblock in OVL_FS()

 Documentation/filesystems/fsverity.rst  |   2 +
 Documentation/filesystems/overlayfs.rst |  72 ++++++++++
 fs/overlayfs/Kconfig                    |   9 ++
 fs/overlayfs/copy_up.c                  |  54 +++++++-
 fs/overlayfs/export.c                   |  36 +++--
 fs/overlayfs/file.c                     |   8 +-
 fs/overlayfs/inode.c                    |   8 +-
 fs/overlayfs/namei.c                    |  89 ++++++++++--
 fs/overlayfs/overlayfs.h                |  66 ++++++++-
 fs/overlayfs/ovl_entry.h                |   9 +-
 fs/overlayfs/params.c                   |  96 +++++++++++--
 fs/overlayfs/super.c                    |  40 ++++--
 fs/overlayfs/util.c                     | 233 ++++++++++++++++++++++++++++++--
 13 files changed, 654 insertions(+), 68 deletions(-)

             reply	other threads:[~2023-08-29 10:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29 10:35 Amir Goldstein [this message]
2023-08-29 18:58 ` [GIT PULL] overlayfs update for 6.6 Linus Torvalds
2023-08-30 19:50 ` pr-tracker-bot
2023-08-30  5:26 Amir Goldstein

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=20230829103512.2245736-1-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.