[PATCH v4 5/9] vfs: Copy shouldn't forbid ranges inside the same file
From: Anna Schumaker <hidden>
Date: 2015-09-29 18:05:08
Also in:
linux-btrfs, linux-fsdevel, linux-nfs
Subsystem:
filesystems (vfs and infrastructure), the rest · Maintainers:
Alexander Viro, Christian Brauner, Linus Torvalds
This is perfectly valid for BTRFS and XFS, so let's leave this up to filesystems to check. Signed-off-by: Anna Schumaker <redacted> Reviewed-by: David Sterba <dsterba-IBi9RG/b67k@public.gmane.org> Reviewed-by: Darrick J. Wong <redacted> --- fs/read_write.c | 4 ---- 1 file changed, 4 deletions(-)
diff --git a/fs/read_write.c b/fs/read_write.c
index f3d6c48..8e7cb33 100644
--- a/fs/read_write.c
+++ b/fs/read_write.c@@ -1371,10 +1371,6 @@ ssize_t vfs_copy_file_range(struct file *file_in, loff_t pos_in, 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; - if (len == 0) return 0;
--
2.5.3
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html