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

From: <bugzilla-noreply_at_freebsd.org>
Date: Wed, 20 Sep 2023 21:24:04 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962

--- Comment #6 from Rick Macklem <rmacklem@FreeBSD.org> ---
It looks like there would need to be a
layering violation, since the code that
goes in kern_copy_file_range() will need
to be specific to shm_ops, since the
range lock code needs to use shm_mtx.
(Or a new f_op specifically for
copy_file_range() would need to be added.)

So, the fallback is not trivial, although
it is not a lot of work.

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