Subject: bug#63850: cp fails for files > 2 GB if copy offload is unsupported

From: Pádraig Brady <[email-masked]>
Date: Tue, 6 Jun 2023 10:53:50 +0100

On 06/06/2023 06:48, Paul Eggert wrote:
> On 2023-06-05 22:26, Sam James wrote:
>> It's just that linux-headers is
>> a special case
> 
> Indeed it is. And apparently glibc avoids the copy_file_range bugs by
> never, ever using copy_file_range internally - which explains why glibc
> hasn't run into this backward compatibility issue. Presumably once glibc
> starts assuming kernel 5.3 or later, it can start using copy_file_range
> internally.

Yes, glibc has the --enable-kernel configure option
to allow setting the compatibility range independently
from the build host (kernel headers).
In my experience a distro needs to support quite a range of kernel versions
mainly due to certain hardware platforms being tied to older kernels.

> Anyway, thanks for explaining. I installed the patch I mentioned into
> Gnulib and have updated coreutils accordingly on Savannah master. Please
> give it a try.

Thanks for making the change Paul.

Pádraig