Date: Fri, 29 Dec 2023 23:01:02 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 273962] copy_file_range does not work on shared memory objects Message-ID: <bug-273962-9-5eXqOOYLAB@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273962-9@https.bugs.freebsd.org/bugzilla/> References: <bug-273962-9@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273962 --- Comment #13 from commit-hook@FreeBSD.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3D84b4342c0d7ac8a3187309a978d41e676= 5154cc1 commit 84b4342c0d7ac8a3187309a978d41e6765154cc1 Author: Rick Macklem <rmacklem@FreeBSD.org> AuthorDate: 2023-12-29 22:59:00 +0000 Commit: Rick Macklem <rmacklem@FreeBSD.org> CommitDate: 2023-12-29 22:59:00 +0000 copy_file_range.2: Clarify that only regular files work PR#273962 reported that copy_file_range(2) did not work on shared memory objects and returned EINVAL. Although the reporter felt this was incorrect, it is what the Linux copy_file_range(2) syscall does. Since there was no collective agreement that the FreeBSD semantics should be changed to no longer be Linux compatible, copy_file_range(2) still works on regular files only. This man page update clarifies that. If, someday, copy_file_range(2) is changed to support non-regular files, then the man page will need to be updated to reflect that. PR: 273962 Reviewed by: karels, pauamma_gundo.com (manpages) MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D43227 lib/libc/sys/copy_file_range.2 | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273962-9-5eXqOOYLAB>