Messages in this thread | ![/](/images/icornerl.gif) | | From | Miklos Szeredi <> | Date | Mon, 24 Jul 2023 15:55:21 +0200 | Subject | Re: [RFC PATCH 1/4] splice: Fix corruption of spliced data after splice() returns |
| |
On Mon, 24 Jul 2023 at 11:44, David Howells <dhowells@redhat.com> wrote: > > Linus Torvalds <torvalds@linux-foundation.org> wrote: > > > > So what's the API that provides the semantics of _copying_? > > > > It's called "read()" and "write()". > > What about copy_file_range()? That seems to fall back to splicing if not > directly implemented by the filesystem. It looks like the manpage for that > needs updating too - or should that actually copy?
Both source and destination of copy_file_range() are regular files and do_splice_direct() is basically equivalent to write(dest, mmap of source), no refd buffers remain beyond the end of the syscall. What is it that should be updated in the manpage?
Thanks, Miklos
| ![\](/images/icornerr.gif) |