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

From: <bugzilla-noreply_at_freebsd.org>
Date: Thu, 21 Sep 2023 01:08:33 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962

--- Comment #8 from Rick Macklem <rmacklem@FreeBSD.org> ---
The most recent Linux man page for copy_file_range(2)
appears to be here:
https://man7.org/linux/man-pages/man2/copy_file_range.2.html

In it:
       EINVAL The flags argument is not 0.

       EINVAL fd_in and fd_out refer to the same file and the source and
              target ranges overlap.

       EINVAL Either fd_in or fd_out is not a regular file.

So, the current implementation appears to be Linux compatible.
(The FreeBSD man page does need to be fixed for the case of
EINVAL being returned for either fd not referring to regular files.)

I have posted to freebsd-fs@ and we'll see whether most others
think that the FreeBSD syscall should remain Linux compatible.
(Which is what is noted at the end of the FreeBSD man page.)

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