mirror of
https://sourceware.org/git/glibc.git
synced 2024-11-09 23:00:07 +00:00
NEWS: clarify copy_file_range
Minor tweak to clarify what applications must do.
This commit is contained in:
parent
6ea21bfe43
commit
7444810387
8
NEWS
8
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
|
support the system call of the same name. Previously, user space
|
||||||
emulation was performed, but its behavior did not match the kernel
|
emulation was performed, but its behavior did not match the kernel
|
||||||
behavior, which was deemed too confusing. Applications which use the
|
behavior, which was deemed too confusing. Applications which use the
|
||||||
copy_file_range function will have to be run on kernels which implement
|
copy_file_range function can no longer rely on glibc to provide a fallback
|
||||||
the copy_file_range system call. Support for most architectures was added
|
on kernels that do not support the copy_file_range system call, and if
|
||||||
in version 4.5 of the mainline Linux kernel.
|
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.
|
||||||
|
|
||||||
* The functions clock_gettime, clock_getres, clock_settime,
|
* The functions clock_gettime, clock_getres, clock_settime,
|
||||||
clock_getcpuclockid, clock_nanosleep were removed from the librt library
|
clock_getcpuclockid, clock_nanosleep were removed from the librt library
|
||||||
|
Loading…
Reference in New Issue
Block a user