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 updates for 6.8
Date: Wed, 10 Jan 2024 18:29:00 +0200 [thread overview]
Message-ID: <20240110162900.174626-1-amir73il@gmail.com> (raw)
Hi Linus,
Please pull overlayfs updates for 6.8.
This is a very small update with no bug fixes and no new features.
The larger update of overlayfs for this cycle, the re-factoring
of overlayfs code into generic backing_file helpers, was already
merged via a PR that I had sent Christian before the merge window.
This branch has been sitting in linux-next for a few weeks and
it has gone through the usual overlayfs test routines.
The branch merges cleanly with master branch of the moment.
Thanks,
Amir.
----------------------------------------------------------------
The following changes since commit 98b1cc82c4affc16f5598d4fa14b1858671b2263:
Linux 6.7-rc2 (2023-11-19 15:02:14 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/overlayfs/vfs.git ovl-update-6.8
for you to fetch changes up to d17bb4620f90f81d8a8a45c3d025c679a1b5efcd:
overlayfs.rst: fix ReST formatting (2023-12-15 12:31:36 +0200)
----------------------------------------------------------------
overlayfs updates for 6.8
- Simplify/clarify some code
No bug fixes here, just some changes following questions from Al
about overlayfs code that could be a little more simple to follow.
- Overlayfs documentation style fixes
Mainly fixes for ReST formatting suggested by documentation developers.
----------------------------------------------------------------
Amir Goldstein (4):
ovl: remove redundant ofs->indexdir member
ovl: initialize ovl_copy_up_ctx.destname inside ovl_do_copy_up()
overlayfs.rst: use consistent feature names
overlayfs.rst: fix ReST formatting
Documentation/filesystems/overlayfs.rst | 104 +++++++++++++++++---------------
fs/overlayfs/copy_up.c | 8 ++-
fs/overlayfs/export.c | 4 +-
fs/overlayfs/namei.c | 4 +-
fs/overlayfs/ovl_entry.h | 5 +-
fs/overlayfs/params.c | 2 -
fs/overlayfs/readdir.c | 2 +-
fs/overlayfs/super.c | 19 +++---
fs/overlayfs/util.c | 2 +-
9 files changed, 76 insertions(+), 74 deletions(-)
next reply other threads:[~2024-01-10 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 16:29 Amir Goldstein [this message]
2024-01-10 20:38 ` [GIT PULL] overlayfs updates for 6.8 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=20240110162900.174626-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).