On Wednesday, 19 July 2023 06:17:51 EDT, Miklos Szeredi wrote:
On Thu, 29 Jun 2023 at 17:56, David Howells <dhowells@xxxxxxxxxx> wrote:
Splicing data from, say, a file into a pipe currently leaves the source
pages in the pipe after splice() returns - but this means that those pages
can be subsequently modified by shared-writable mmap(), write(),
fallocate(), etc. before they're consumed.
What is this trying to fix? The above behavior is well known, so
it's not likely to be a problem.
Respectfully, it's not well-known, as it's not documented. If the splice(2)
man page had mentioned that pages can be mutated after they're already
ostensibly at rest in the output pipe buffer, then my nightly backups
wouldn't have been incurring corruption silently for many months.
