[Bug 273962] copy_file_range does not work on shared memory objects

From: <bugzilla-noreply_at_freebsd.org>
Date: Thu, 11 Jan 2024 01:21:29 UTC

--- Comment #15 from commit-hook@FreeBSD.org ---
A commit in branch stable/13 references this bug:


commit 6561a7141b5603235d18538f6c66322ed7fc67d3
Author:     Rick Macklem <rmacklem@FreeBSD.org>
AuthorDate: 2023-12-29 22:59:00 +0000
Commit:     Rick Macklem <rmacklem@FreeBSD.org>
CommitDate: 2024-01-11 01:20:35 +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

    (cherry picked from commit 84b4342c0d7ac8a3187309a978d41e6765154cc1)

 lib/libc/sys/copy_file_range.2 | 18 +++++++++++++-----
 1 file changed, 13 insertions(+), 5 deletions(-)

You are receiving this mail because:
You are on the CC list for the bug.