Message ID | 1442003423-6884-8-git-send-email-Anna.Schumaker@Netapp.com (mailing list archive) |
---|---|
State | Not Applicable |
Headers | show |
On Fri, Sep 11, 2015 at 04:30:20PM -0400, Anna Schumaker wrote: > I still want to do an in-kernel copy even if the files are on different > mountpoints, and NFS has a "server to server" copy that expects two > files on different mountpoints. Let's have individual filesystems > implement this check instead. > > Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com> The cross-fs checks exist in the btrfs callback, Reviewed-by: David Sterba <dsterba@suse.com> -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/fs/read_write.c b/fs/read_write.c index ac32388..363bd3e 100644 --- a/fs/read_write.c +++ b/fs/read_write.c @@ -1366,11 +1366,6 @@ ssize_t vfs_copy_file_range(struct file *file_in, loff_t pos_in, pos_in + len > i_size_read(inode_in)) return -EINVAL; - /* this could be relaxed once a method supports cross-fs copies */ - if (inode_in->i_sb != inode_out->i_sb || - file_in->f_path.mnt != file_out->f_path.mnt) - return -EXDEV; - if (len == 0) return 0;
I still want to do an in-kernel copy even if the files are on different mountpoints, and NFS has a "server to server" copy that expects two files on different mountpoints. Let's have individual filesystems implement this check instead. Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com> --- fs/read_write.c | 5 ----- 1 file changed, 5 deletions(-)