Matt Whitlock <kernel@xxxxxxxxxxxxxxxxx> wrote: > In other words, the currently implemented behavior is appropriate for > SPLICE_F_MOVE, but it is not appropriate for ~SPLICE_F_MOVE. The problems with SPLICE_F_MOVE is that it's only applicable to splicing *out* of a pipe. By the time you get that far the pages can already be corrupted by a shared-writable mmap or write(). David
