Date: Wed, 19 Jun 2019 23:56:02 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: "freebsd-fs@freebsd.org" <freebsd-fs@FreeBSD.org> Subject: RFC: should a copy_file_range(2) syscall work across multiple file systems? Message-ID: <YTXPR01MB02853C73E79C0A5CFEE636E8DDE50@YTXPR01MB0285.CANPRD01.PROD.OUTLOOK.COM>
next in thread | raw e-mail | index | archive | help
I have been working on a copy_file_range(2) syscall for FreeBSD, which is m= eant to be compatible with the Linux one. (Current patch is at https://reviews.freebsd.org/D20584) One thing the current patch does do is allow the kernel copy to be done acr= oss multiple file systems (ie. source and destination files on different file s= ystems). The Linux syscall *may* not allow this. The man page specifies EXDEV as an error return, but discussion of the Linux syscall suggests that it may be (= or has already been) modified to work across multiple file systems. I thought that this would be a useful feature, but does require the default code to be above the VOP_xxx() layer and *might* not be Linux compatible. (The incompatibility would be working for cases where the Linux syscall mig= ht not.) So, should it work across multiple file systems? rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTXPR01MB02853C73E79C0A5CFEE636E8DDE50>