From: Amir Goldstein <amir73il@gmail.com>
To: Christian Brauner <brauner@kernel.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Daan De Meyer <daan.j.demeyer@gmail.com>,
linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [RFC][PATCH 4/5] ovl: add support for copy file range from another fs
Date: Thu, 23 Jul 2026 13:48:47 +0200 [thread overview]
Message-ID: <20260723114848.1212429-5-amir73il@gmail.com> (raw)
In-Reply-To: <20260723114848.1212429-1-amir73il@gmail.com>
It is technically possible for overlayfs to copy_file_range() from
the base fs of the real layer.
Set the vfs flag FOP_CROSS_FS_COPY and implement copy from another fs.
Implementation of copy to another fs is a bit more subtle and will be
handled by a followup patch.
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
---
fs/overlayfs/file.c | 22 ++++++++++++++++++++++
fs/overlayfs/ovl_entry.h | 7 ++++++-
2 files changed, 28 insertions(+), 1 deletion(-)
diff --git a/fs/overlayfs/file.c b/fs/overlayfs/file.c
index f3d97eb146e85..169a48de565e9 100644
--- a/fs/overlayfs/file.c
+++ b/fs/overlayfs/file.c
@@ -533,6 +533,13 @@ static loff_t ovl_copyfile(struct file *file_in, loff_t pos_in,
struct file *realfile_in, *realfile_out;
loff_t ret;
+ /*
+ * Overlayfs may be able to copy to a non overlayfs dst which is on the
+ * same sb or same fs type as real file_in fs, but not implemented yet.
+ */
+ if (WARN_ON_ONCE(!is_ovl_fs(inode_out->i_sb)))
+ return -EXDEV;
+
inode_lock(inode_out);
if (op != OVL_DEDUPE) {
/* Update mode */
@@ -547,6 +554,19 @@ static loff_t ovl_copyfile(struct file *file_in, loff_t pos_in,
if (IS_ERR(realfile_out))
goto out_unlock;
+ /*
+ * Overlayfs may be able to copy from a non overlayfs src which is on
+ * the same sb or same fs type as upper fs.
+ */
+ if (unlikely(!is_ovl_fs(inode_in->i_sb))) {
+ if (WARN_ON_ONCE(op != OVL_COPY)) {
+ ret = -EXDEV;
+ goto out_unlock;
+ }
+ realfile_in = file_in;
+ goto do_copy;
+ }
+
realfile_in = ovl_real_file(file_in);
ret = PTR_ERR(realfile_in);
if (IS_ERR(realfile_in))
@@ -565,6 +585,7 @@ static loff_t ovl_copyfile(struct file *file_in, loff_t pos_in,
}
}
+do_copy:
with_ovl_creds(inode_out->i_sb) {
switch (op) {
case OVL_COPY:
@@ -660,6 +681,7 @@ const struct file_operations ovl_file_operations = {
.splice_read = ovl_splice_read,
.splice_write = ovl_splice_write,
+ .fop_flags = FOP_CROSS_FS_COPY,
.copy_file_range = ovl_copy_file_range,
.remap_file_range = ovl_remap_file_range,
.setlease = generic_setlease,
diff --git a/fs/overlayfs/ovl_entry.h b/fs/overlayfs/ovl_entry.h
index 80cad4ea96a3e..8a1862cf87d78 100644
--- a/fs/overlayfs/ovl_entry.h
+++ b/fs/overlayfs/ovl_entry.h
@@ -112,10 +112,15 @@ static inline struct mnt_idmap *ovl_upper_mnt_idmap(struct ovl_fs *ofs)
extern struct file_system_type ovl_fs_type;
+static inline bool is_ovl_fs(const struct super_block *sb)
+{
+ return sb->s_type == &ovl_fs_type;
+}
+
static inline struct ovl_fs *OVL_FS(struct super_block *sb)
{
if (IS_ENABLED(CONFIG_OVERLAY_FS_DEBUG))
- WARN_ON_ONCE(sb->s_type != &ovl_fs_type);
+ WARN_ON_ONCE(!is_ovl_fs(sb));
return (struct ovl_fs *)sb->s_fs_info;
}
--
2.54.0
next prev parent reply other threads:[~2026-07-23 11:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 11:48 [RFC][PATCH 0/5] Proposal for Cross-fs copy_file_range() Amir Goldstein
2026-07-23 11:48 ` [RFC][PATCH 1/5] fs: clarify cross-sb copy_file_range() code Amir Goldstein
2026-07-23 11:48 ` [RFC][PATCH 2/5] fs: add support for copy file range from another fs Amir Goldstein
2026-07-23 11:48 ` [RFC][PATCH 3/5] fs: add support for copy file range to " Amir Goldstein
2026-07-23 11:48 ` Amir Goldstein [this message]
2026-07-23 11:48 ` [RFC][PATCH 5/5] ovl: " Amir Goldstein
2026-07-23 13:05 ` [RFC][PATCH 0/5] Proposal for Cross-fs copy_file_range() Daan De Meyer
2026-07-23 13:36 ` Amir Goldstein
2026-07-23 13:54 ` Daan De Meyer
2026-07-23 14:17 ` Amir Goldstein
2026-07-23 23:29 ` Gao Xiang
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=20260723114848.1212429-5-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=daan.j.demeyer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox