https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962
--- Comment #6 from Rick Macklem <rmack...@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 the assignee for the bug.
