From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>,
Dave Chinner <david@fromorbit.com>,
linux-unionfs@vger.kernel.org
Cc: Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org,
"Darrick J . Wong" <darrick.wong@oracle.com>,
linux-fsdevel@vger.kernel.org
Subject: [PATCH v2 3/4] vfs: allow vfs_copy_file_range() across file systems
Date: Mon, 12 Sep 2016 18:06:42 +0300 [thread overview]
Message-ID: <1473692803-11964-4-git-send-email-amir73il@gmail.com> (raw)
In-Reply-To: <1473692803-11964-1-git-send-email-amir73il@gmail.com>
copy_file_range syscall returns -EXDEV if src and dest
file are not on the same file system.
The vfs_copy_file_range() helper, however, knows how to copy
across file systems with do_splice_direct().
Move the enforcement of same file system from the vfs helper
to the syscall code.
A following patch is going to use the vfs_copy_file_range()
helper in overlayfs to copy up between lower and upper
not on the same file system.
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
---
fs/read_write.c | 15 ++++++++++-----
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/fs/read_write.c b/fs/read_write.c
index 9dc6e52..c4675c6 100644
--- a/fs/read_write.c
+++ b/fs/read_write.c
@@ -1502,10 +1502,6 @@ ssize_t vfs_copy_file_range(struct file *file_in, loff_t pos_in,
(file_out->f_flags & O_APPEND))
return -EBADF;
- /* this could be relaxed once a method supports cross-fs copies */
- if (inode_in->i_sb != inode_out->i_sb)
- return -EXDEV;
-
if (len == 0)
return 0;
@@ -1514,7 +1510,8 @@ ssize_t vfs_copy_file_range(struct file *file_in, loff_t pos_in,
return ret;
ret = -EOPNOTSUPP;
- if (file_out->f_op->copy_file_range)
+ if (inode_in->i_sb == inode_out->i_sb &&
+ file_out->f_op->copy_file_range)
ret = file_out->f_op->copy_file_range(file_in, pos_in, file_out,
pos_out, len, flags);
if (ret == -EOPNOTSUPP)
@@ -1569,6 +1566,14 @@ SYSCALL_DEFINE6(copy_file_range, int, fd_in, loff_t __user *, off_in,
pos_out = f_out.file->f_pos;
}
+ /*
+ * FIXME: should copy_file_range syscall enforce that src and
+ * dest files are on the same mount point or only on the same
+ * file system? none of the above?
+ */
+ if (file_inode(f_in.file)->i_sb != file_inode(f_out.file)->i_sb)
+ return -EXDEV;
+
ret = vfs_copy_file_range(f_in.file, pos_in, f_out.file, pos_out, len,
flags);
if (ret > 0) {
--
2.7.4
next prev parent reply other threads:[~2016-09-12 15:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 15:29 [PATCH] ovl: use copy_file_range for copy up if possible Amir Goldstein
2016-09-08 20:25 ` Dave Chinner
2016-09-09 7:31 ` Amir Goldstein
2016-09-09 7:54 ` Dave Chinner
2016-09-09 8:27 ` Amir Goldstein
2016-09-09 23:52 ` Dave Chinner
2016-09-10 7:40 ` Christoph Hellwig
2016-09-10 18:15 ` Amir Goldstein
2016-09-10 18:54 ` Amir Goldstein
2016-09-11 22:11 ` Dave Chinner
2016-09-12 6:52 ` Amir Goldstein
2016-09-12 15:37 ` Amir Goldstein
2016-09-12 15:06 ` [PATCH v2 0/4] ovl: efficient copy up by reflink Amir Goldstein
2016-09-12 15:06 ` [PATCH v2 1/4] vfs: allow vfs_clone_file_range() across mount points Amir Goldstein
2016-09-12 15:06 ` [PATCH v2 2/4] ovl: use vfs_clone_file_range() for copy up if possible Amir Goldstein
2016-09-13 0:02 ` Dave Chinner
2016-09-13 6:47 ` Amir Goldstein
2016-09-12 15:06 ` Amir Goldstein [this message]
2016-09-13 0:08 ` [PATCH v2 3/4] vfs: allow vfs_copy_file_range() across file systems Dave Chinner
2016-09-13 7:01 ` Amir Goldstein
2016-09-12 15:06 ` [PATCH v2 4/4] ovl: use vfs_copy_file_range() to copy up file data Amir Goldstein
2016-09-13 0:11 ` Dave Chinner
2016-09-13 7:26 ` Amir Goldstein
2016-09-14 12:43 ` Amir Goldstein
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=1473692803-11964-4-git-send-email-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).