All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Christian Brauner <brauner@kernel.org>,
	Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, linux-unionfs@vger.kernel.org
Subject: [RFC][PATCH 0/4] Intruduce stacking filesystem vfs helpers
Date: Thu, 21 Dec 2023 11:54:06 +0200	[thread overview]
Message-ID: <20231221095410.801061-1-amir73il@gmail.com> (raw)

Christian,

These patches essentially just lift some overlayfs code to common
file fs/backing_file.c.

They are based on vfs.rw and overlayfs-next branches.

The motivation is (per Miklos' request) to reuse common stacking code
for the FUSE passthrough patches that I am shaping up for upstream.

I have been testing those patches with my fuse-backing-fd development
branch [1] for quite some time and I think both you and Miklos gave
a conceptual ACK to some version of this work, but the patches were
never publicly posted.

I am aiming the FUSE passthough work for the 6.9 dev cycle and I was
contemplating whether I should queue these up for 6.8 merge window to
give them time to mature before 6.9 merge window.

If I do that, would you preffer to take these patches via the vfs tree
or will you be ok with me including them in the overlayfs PR for 6.8?

Miklos,

Are you ok with including this in overlayfs PR for 6.8?

Thanks,
Amir.

[1] https://github.com/amir73il/linux/commits/fuse-backing-fd

Amir Goldstein (4):
  fs: prepare for stackable filesystems backing file helpers
  fs: factor out backing_file_{read,write}_iter() helpers
  fs: factor out backing_file_splice_{read,write}() helpers
  fs: factor out backing_file_mmap() helper

 MAINTAINERS                  |   9 +
 fs/Kconfig                   |   4 +
 fs/Makefile                  |   1 +
 fs/backing-file.c            | 324 +++++++++++++++++++++++++++++++++++
 fs/open.c                    |  38 ----
 fs/overlayfs/Kconfig         |   1 +
 fs/overlayfs/file.c          | 245 ++++----------------------
 fs/overlayfs/overlayfs.h     |   8 +-
 fs/overlayfs/super.c         |  11 +-
 include/linux/backing-file.h |  42 +++++
 include/linux/fs.h           |   3 -
 11 files changed, 423 insertions(+), 263 deletions(-)
 create mode 100644 fs/backing-file.c
 create mode 100644 include/linux/backing-file.h

-- 
2.34.1


             reply	other threads:[~2023-12-21  9:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21  9:54 Amir Goldstein [this message]
2023-12-21  9:54 ` [RFC][PATCH 1/4] fs: prepare for stackable filesystems backing file helpers Amir Goldstein
2023-12-21  9:54 ` [RFC][PATCH 2/4] fs: factor out backing_file_{read,write}_iter() helpers Amir Goldstein
2023-12-21  9:54 ` [RFC][PATCH 3/4] fs: factor out backing_file_splice_{read,write}() helpers Amir Goldstein
2023-12-21  9:54 ` [RFC][PATCH 4/4] fs: factor out backing_file_mmap() helper Amir Goldstein
2023-12-22 12:54   ` Christian Brauner
2023-12-23  6:54     ` Amir Goldstein
2023-12-23  6:56       ` Amir Goldstein
2023-12-23 13:04         ` Christian Brauner
2023-12-23 14:28           ` Amir Goldstein
2023-12-22 12:44 ` [RFC][PATCH 0/4] Intruduce stacking filesystem vfs helpers Christian Brauner
2023-12-23  8:07   ` Amir Goldstein
2023-12-23 13:11     ` Christian Brauner

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=20231221095410.801061-1-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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.