RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1724975 - glibc: Remove copy_file_range emulation
Summary: glibc: Remove copy_file_range emulation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: glibc
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.1
Assignee: Carlos O'Donell
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On: 1724976
Blocks: 1684559
TreeView+ depends on / blocked
 
Reported: 2019-06-28 07:54 UTC by Florian Weimer
Modified: 2023-07-18 14:30 UTC (History)
7 users (show)

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.
Clone Of:
: 1724976 (view as bug list)
Environment:
Last Closed: 2019-11-05 21:29:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:3513 0 None None None 2019-11-05 21:29:23 UTC
Sourceware 24744 0 P2 RESOLVED Remove copy_file_range emulation 2020-08-04 13:40:02 UTC

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
Note You need to log in before you can comment on or make changes to this bug.