linux.git/fs/remap_range.c, branch v5.10 Linux kernel source tree vfs: move the remap range helpers to remap_range.c 2020-10-15T16:48:49+00:00 Darrick J. Wong darrick.wong@oracle.com 2020-10-14T23:38:47+00:00 1b2c54d63cde7e8cf15aa6319aba168d81c7e364 Complete the migration by moving the file remapping helper functions out of read_write.c and into remap_range.c. This reduces the clutter in the first file and (eventually) will make it so that we can compile out the second file if it isn't needed. Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> 
Complete the migration by moving the file remapping helper functions out
of read_write.c and into remap_range.c.  This reduces the clutter in the
first file and (eventually) will make it so that we can compile out the
second file if it isn't needed.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
vfs: move generic_remap_checks out of mm 2020-10-14T23:47:08+00:00 Darrick J. Wong darrick.wong@oracle.com 2020-10-14T23:47:08+00:00 02e83f46ebfaf9405881e290794c913d457541f0 I would like to move all the generic helpers for the vfs remap range functionality (aka clonerange and dedupe) into a separate file so that they won't be scattered across the vfs and the mm subsystems. The eventual goal is to be able to deselect remap_range.c if none of the filesystems need that code, but the tricky part here is picking a stable(ish) part of the merge window to rearrange code. Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> 
I would like to move all the generic helpers for the vfs remap range
functionality (aka clonerange and dedupe) into a separate file so that
they won't be scattered across the vfs and the mm subsystems.  The
eventual goal is to be able to deselect remap_range.c if none of the
filesystems need that code, but the tricky part here is picking a
stable(ish) part of the merge window to rearrange code.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>