| From: |
| Goldwyn Rodrigues <rgoldwyn-AT-suse.de> |
| To: |
| linux-fsdevel-AT-vger.kernel.org |
| Subject: |
| [PATCH v2 0/4] Enable holes in copy_file_range() |
| Date: |
| Wed, 9 May 2018 20:58:16 -0500 |
| Message-ID: |
| <20180510015820.17700-1-rgoldwyn@suse.de> |
| Cc: |
| hch-AT-lst.de, linux-unionfs-AT-vger.kernel.org, david-AT-fromorbit.com, viro-AT-zeniv.linux.org.uk |
| Archive-link: |
| Article |
If copy_file_range performs a copy using splice, it converts holes
to zeros. This effort primarily changes this behavior to create
holes when it is possible.
Even if copy_file_range() or clone_file_range() does not work for different
mounted filesystems, We should be able to splice files if they do not
belong the same super_block.
Changes since v1:
- Fixed bug when hole/data offset is farther than len
- [Amir] Refactor flags parameter
Changes since v0:
- [Amir] Carved out do_copy_file_range() which can be used by overlayfs
--
Goldwyn
