This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [patch] NEWS: clarify copy_file_range
- From: DJ Delorie <dj at redhat dot com>
- To: Florian Weimer <fw at deneb dot enyo dot de>
- Cc: libc-alpha at sourceware dot org
- Date: Mon, 08 Jul 2019 17:41:58 -0400
- Subject: Re: [patch] NEWS: clarify copy_file_range
>> diff --git a/NEWS b/NEWS
>> index 6c7de105ac..11099f7248 100644
>> --- a/NEWS
>> +++ b/NEWS
>> @@ -46,9 +46,11 @@ Deprecated and removed features, and other changes affecting compatibility:
>> support the system call of the same name. Previously, user space
>> emulation was performed, but its behavior did not match the kernel
>> behavior, which was deemed too confusing. Applications which use the
>> - copy_file_range function will have to be run on kernels which implement
>> - the copy_file_range system call. Support for most architectures was added
>> - in version 4.5 of the mainline Linux kernel.
>> + copy_file_range function can no longer rely on glibc to provide a fallback
>> + on kernels that do not support the copy_file_range system call, and if
>> + this function returns ENOSYS, they will need to use their own fallback.
>> + Support for copy_file_range for most architectures was added in version
>> + 4.5 of the mainline Linux kernel.
Florian Weimer <fw@deneb.enyo.de> writes:
> Looks good to me. Thanks.
NP; pushed.