Return-Path: Received: from mx142.netapp.com ([216.240.21.19]:10583 "EHLO mx142.netapp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760576AbbIDURY (ORCPT ); Fri, 4 Sep 2015 16:17:24 -0400 From: Anna Schumaker To: , , , , , , , , , , Subject: [PATCH v1 5/8] vfs: Remove copy_file_range mountpoint checks Date: Fri, 4 Sep 2015 16:16:59 -0400 Message-ID: <1441397823-1203-6-git-send-email-Anna.Schumaker@Netapp.com> In-Reply-To: <1441397823-1203-1-git-send-email-Anna.Schumaker@Netapp.com> References: <1441397823-1203-1-git-send-email-Anna.Schumaker@Netapp.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-nfs-owner@vger.kernel.org List-ID: 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 --- fs/read_write.c | 5 ----- 1 file changed, 5 deletions(-) diff --git a/fs/read_write.c b/fs/read_write.c index 82c4933..922ca58 100644 --- a/fs/read_write.c +++ b/fs/read_write.c @@ -1369,11 +1369,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; - /* forbid ranges in the same file */ if (inode_in == inode_out) return -EINVAL; -- 2.5.1