Subject: bug#24399: FICLONE for coreutils; copy_file_range?

From: Paul Eggert <[email-masked]>
Date: Sat, 10 Sep 2016 19:18:17 -0700

Pádraig Brady wrote:

> One quite awkward thing at present is if the file system doesn't
> implement the syscall, it falls back to do_splice_direct
> which is basically sendfile(), and that will expand holes.

OK, thanks for the info. It sounds like copy_file_range is not ready for 
prime-time, then. Its use of a size_t to represent a file size seems like it is 
obviously wrong, as well.