From: Christian Brauner <brauner@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel@vger.kernel.org, linux-unionfs@vger.kernel.org
Subject: Re: [RFC][PATCH 0/4] Intruduce stacking filesystem vfs helpers
Date: Fri, 22 Dec 2023 13:44:30 +0100 [thread overview]
Message-ID: <20231222-bekennen-unrat-a42e50abe5de@brauner> (raw)
In-Reply-To: <20231221095410.801061-1-amir73il@gmail.com>
> If I do that, would you preffer to take these patches via the vfs tree
I would prefer if you:
* Add the vfs infrastructure stuff on top of what's in vfs.file.
There's also currently a conflict between this series and what's in there.
* Pull vfs.file into overlayfs.
* Port overlayfs to the new infrastructure.
io_uring already depends on vfs.file as well.
If this is straightforward I can include it in v6.8. The VFS prs will go
out the week before January 7.
next prev parent reply other threads:[~2023-12-22 12:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 9:54 [RFC][PATCH 0/4] Intruduce stacking filesystem vfs helpers Amir Goldstein
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 ` Christian Brauner [this message]
2023-12-23 8:07 ` [RFC][PATCH 0/4] Intruduce stacking filesystem vfs helpers 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=20231222-bekennen-unrat-a42e50abe5de@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--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.