public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 220489] New: copy_file_range glibc user-space emulation in versions 2.27-2.29 only
Date: Mon, 25 Aug 2025 06:40:11 +0000	[thread overview]
Message-ID: <bug-220489-11311@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=220489

            Bug ID: 220489
           Summary: copy_file_range glibc user-space emulation in versions
                    2.27-2.29 only
           Product: Documentation
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: low
          Priority: P3
         Component: man-pages
          Assignee: documentation_man-pages@kernel-bugs.osdl.org
          Reporter: hvtaifwkbgefbaei@gmail.com
        Regression: No

Current version of the man page: "Linux 4.5, but glibc 2.27 provides a
user-space emulation when it is not available."

However, glibc 2.30 changelog:
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 for most
architectures was added in version 4.5 of the mainline Linux kernel.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2025-08-25  6:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25  6:40 bugzilla-daemon [this message]
2025-10-25 18:57 ` [Bug 220489] copy_file_range glibc user-space emulation in versions 2.27-2.29 only bugzilla-daemon
2025-10-29  2:40 ` bugzilla-daemon
2025-11-09 20:13 ` bugzilla-daemon
2025-11-24 16:45 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-220489-11311@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-man@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox