Bug 1724975

Summary: glibc: Remove copy_file_range emulation
Product: Red Hat Enterprise Linux 8 Reporter: Florian Weimer <fweimer>
Component: glibcAssignee: Carlos O'Donell <codonell>
Status: CLOSED ERRATA QA Contact: qe-baseos-tools-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: ---CC: ashankar, codonell, dj, fweimer, mnewsome, pfrankli, skolosov
Target Milestone: rc   
Target Release: 8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glibc-2.28-71.el8 Doc Type: Bug Fix
Doc Text:
The copy_file_range function fails with ENOSYS if the kernel does not 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 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 is present for all architectures when using a supported Red Hat Enterprise Linux kernel.
 Story Points: ---
Clone Of:
: 1724976 (view as bug list) Environment:
Last Closed: 2019-11-05 21:29:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1724976    
Bug Blocks: 1684559    

Description Florian Weimer 2019-06-28 07:54:32 UTC 
For alignment with upstream, we should remove the copy_file_range emulation in glibc.  This will prevent people from running into bugs in the emulation.

copy_file_range was backported into kernel-3.10.0-693.el7, so this change does not affect current Red Hat Enterprise Linux 7 kernel hosts.
Comment 2 Sergey Kolosov 2019-09-23 16:11:07 UTC 
Verified on x86_64 and ppc64le on kernel 3.10.0-514.el7, with static compiled test program which calls copy-file-range(), a sanity check on s390x and aarch64.
Comment 4 errata-xmlrpc 2019-11-05 21:29:05 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3513