vfs: allow some remap flags to be passed to vfs_clone_file_range
authorDarrick J. Wong <darrick.wong@oracle.com>
Fri, 30 Nov 2018 20:32:38 +0000 (12:32 -0800)
committerDarrick J. Wong <darrick.wong@oracle.com>
Tue, 4 Dec 2018 16:50:49 +0000 (08:50 -0800)
commit6744557b53a2b710ebce3736a5c27a0119685fcc
tree0ac2f8aa8dbdb860b34faa7274e723004fff2b00
parent7d048df4e9b05ba89b74d062df59498aa81f3785
vfs: allow some remap flags to be passed to vfs_clone_file_range

In overlayfs, ovl_remap_file_range calls vfs_clone_file_range on the
lower filesystem's inode, passing through whatever remap flags it got
from its caller.  Since vfs_copy_file_range first tries a filesystem's
remap function with REMAP_FILE_CAN_SHORTEN, this can get passed through
to the second vfs_copy_file_range call, and this isn't an issue.
Change the WARN_ON to look only for the DEDUP flag.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Reviewed-by: Amir Goldstein <amir73il@gmail.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
fs/read_write.c