Date: Wed, 20 Sep 2023 21:24:04 +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-maKAta9T1l@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 #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. --=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-maKAta9T1l>