Return-Path: Received: from mx144.netapp.com ([216.240.21.25]:47116 "EHLO mx144.netapp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933263AbbIYUse (ORCPT ); Fri, 25 Sep 2015 16:48:34 -0400 From: Anna Schumaker To: , , , , , , , , , , Subject: [PATCH v3 7/9] vfs: Remove copy_file_range mountpoint checks Date: Fri, 25 Sep 2015 16:48:13 -0400 Message-ID: <1443214096-12769-8-git-send-email-Anna.Schumaker@Netapp.com> In-Reply-To: <1443214096-12769-1-git-send-email-Anna.Schumaker@Netapp.com> References: <1443214096-12769-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 Reviewed-by: David Sterba --- fs/read_write.c | 5 ----- 1 file changed, 5 deletions(-) diff --git a/fs/read_write.c b/fs/read_write.c index 6f74f1f..ee9fa37 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; -- 2.5.3