Date: Wed, 20 Sep 2023 13:47:29 -0700 From: Rick Macklem <rick.macklem@gmail.com> To: Freebsd fs <freebsd-fs@freebsd.org> Subject: RFC: Should copy_file_range(2) work for shared memory objects? Message-ID: <CAM5tNy4HxY8LK0f6baGhu=opoC3-4ODhqNyxoyPY8vdwxGs5Xg@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Right now (as noted by PR#273962) copy_file_range(2) fails for shared memory objects because there is no vnode (f_vnode == NULL) for them and the code uses vnodes (including a file system specific VOP_COPY_FILE_RANGE(9)). Do you think copy_file_range(2) should work for shared memory objects? This would require specific handling in kern_copy_file_range() to work. I do not think the patch would be a lot of work, but I am not familiar with the f_ops and shared memory code. rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM5tNy4HxY8LK0f6baGhu=opoC3-4ODhqNyxoyPY8vdwxGs5Xg>