https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273962
--- Comment #5 from Rick Macklem <rmack...@freebsd.org> --- I looked and doing the fallback will require some messing about. shm_read() and shm_write() do range locking however copy_file_ramge() needs to do range locking on both fds before copying. I think variants of shm_read() and shm_write() would need to be created without the range locking so that kern_copy_file_range() can call those. kern_copy_file_range() will also need to use rangelock_rlock(), rangelock_tryrlock() and rangelock_wlock() etc for this case. -- You are receiving this mail because: You are the assignee for the bug.