diff options
author | Amir Goldstein <[email protected]> | 2019-06-05 08:04:50 -0700 |
---|---|---|
committer | Darrick J. Wong <[email protected]> | 2019-06-09 10:06:20 -0700 |
commit | 5dae222a5ff0c269730393018a5539cc970a4726 (patch) | |
tree | e1e4e1634de00d8fb7668f575d7e25acace6518f /scripts/gdb/linux/timerlist.py | |
parent | 8c3f406c097b83846c7d18438a905b49d17ae528 (diff) |
vfs: allow copy_file_range to copy across devices
We want to enable cross-filesystem copy_file_range functionality
where possible, so push the "same superblock only" checks down to
the individual filesystem callouts so they can make their own
decisions about cross-superblock copy offload and fallack to
generic_copy_file_range() for cross-superblock copy.
[Amir] We do not call ->remap_file_range() in case the files are not
on the same sb and do not call ->copy_file_range() in case the files
do not belong to the same filesystem driver.
This changes behavior of the copy_file_range(2) syscall, which will
now allow cross filesystem in-kernel copy. CIFS already supports
cross-superblock copy, between two shares to the same server. This
functionality will now be available via the copy_file_range(2) syscall.
Cc: Steve French <[email protected]>
Signed-off-by: Dave Chinner <[email protected]>
Signed-off-by: Amir Goldstein <[email protected]>
Reviewed-by: Darrick J. Wong <[email protected]>
Signed-off-by: Darrick J. Wong <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/timerlist.py')
0 files changed, 0 insertions, 0 deletions