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.7
Date: Mon, 6 Nov 2023 08:50:45 +0200 [thread overview]
Message-ID: <20231106065045.895874-1-amir73il@gmail.com> (raw)
Hi Linus,
Please pull overlayfs update for 6.7.
Most of the changes in this update have been sitting in linux-next for
several weeks, based on two prerequisite vfs topic branches.
Last week, after the vfs branches were merged, I rebased overlayfs-next
to reduce noise.
Last week, I also added patches for new mount options to replace the
lowerdir append syntax that we disabled in v6.6-rc6 and v6.5.8.
This branch has gone through the usual overlayfs test routines and it
merges cleanly with master branch of the moment.
Thanks,
Amir.
----------------------------------------------------------------
The following changes since commit 14ab6d425e80674b6a0145f05719b11e82e64824:
Merge tag 'vfs-6.7.ctime' of gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs (2023-10-30 09:47:13 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/overlayfs/vfs.git ovl-update-6.7
for you to fetch changes up to 24e16e385f2272b1a9df51337a5c32d28a29c7ad:
ovl: add support for appending lowerdirs one by one (2023-10-31 00:13:02 +0200)
----------------------------------------------------------------
overlayfs update for 6.7
Contains the following patch sets:
- Overlayfs aio cleanups and fixes [1]
- Overlayfs lock ordering changes [2]
- Add support for nesting overlayfs private xattrs [3]
- Add new mount options for appending lowerdirs [4]
[1] https://lore.kernel.org/r/20230912173653.3317828-1-amir73il@gmail.com/
[2] https://lore.kernel.org/r/20230816152334.924960-1-amir73il@gmail.com/
[3] https://lore.kernel.org/r/cover.1694512044.git.alexl@redhat.com/
[4] https://lore.kernel.org/r/20231030120419.478228-1-amir73il@gmail.com/
----------------------------------------------------------------
Alexander Larsson (4):
ovl: Add OVL_XATTR_TRUSTED/USER_PREFIX_LEN macros
ovl: Support escaped overlay.* xattrs
ovl: Add an alternative type of whiteout
ovl: Add documentation on nesting of overlayfs mounts
Amir Goldstein (14):
ovl: use simpler function to convert iocb to rw flags
ovl: propagate IOCB_APPEND flag on writes to realfile
ovl: punt write aio completion to workqueue
ovl: protect copying of realinode attributes to ovl inode
ovl: add helper ovl_file_modified()
ovl: split ovl_want_write() into two helpers
ovl: reorder ovl_want_write() after ovl_inode_lock()
ovl: do not open/llseek lower file with upper sb_writers held
ovl: do not encode lower fh with upper sb_writers held
ovl: Move xattr support to new xattrs.c file
ovl: remove unused code in lowerdir param parsing
ovl: store and show the user provided lowerdir mount option
ovl: refactor layer parsing helpers
ovl: add support for appending lowerdirs one by one
Documentation/filesystems/overlayfs.rst | 40 +++-
fs/overlayfs/Makefile | 2 +-
fs/overlayfs/copy_up.c | 142 +++++++++-----
fs/overlayfs/dir.c | 64 +++----
fs/overlayfs/export.c | 7 +-
fs/overlayfs/file.c | 88 ++++++---
fs/overlayfs/inode.c | 165 ++--------------
fs/overlayfs/namei.c | 52 ++++--
fs/overlayfs/overlayfs.h | 72 +++++--
fs/overlayfs/params.c | 322 +++++++++++++++++---------------
fs/overlayfs/params.h | 1 +
fs/overlayfs/readdir.c | 27 ++-
fs/overlayfs/super.c | 92 ++-------
fs/overlayfs/util.c | 115 +++++++++++-
fs/overlayfs/xattrs.c | 271 +++++++++++++++++++++++++++
fs/super.c | 1 +
16 files changed, 929 insertions(+), 532 deletions(-)
create mode 100644 fs/overlayfs/xattrs.c
next reply other threads:[~2023-11-06 6:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 6:50 Amir Goldstein [this message]
2023-11-07 19:54 ` [GIT PULL] overlayfs update for 6.7 Linus Torvalds
2023-11-07 21:07 ` Amir Goldstein
2023-11-07 20:34 ` 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=20231106065045.895874-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 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 read-only IMAP folder(s) and NNTP newsgroup(s).