Date: Wed, 20 Sep 2023 21:16:30 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 273962] copy_file_range does not work on shared memory objects Message-ID: <bug-273962-9-cPuyoaqA68@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273962-9@https.bugs.freebsd.org/bugzilla/> References: <bug-273962-9@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273962 --- Comment #5 from Rick Macklem <rmacklem@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. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273962-9-cPuyoaqA68>