On 2019-07-05 02:28, Rick Macklem wrote: > I am thinking that copy_file_range(2) should do this also. > However, if it returns an error, it is impossible for the caller to know how much > of the data range got copied. How can you kill a program stuck on copy_file_range(2) w/o catching signals? --HPS