[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <63041.1690191864@warthog.procyon.org.uk>
Date: Mon, 24 Jul 2023 10:44:24 +0100
From: David Howells <dhowells@...hat.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: dhowells@...hat.com, Matthew Wilcox <willy@...radead.org>,
Miklos Szeredi <miklos@...redi.hu>,
Matt Whitlock <kernel@...twhitlock.name>,
netdev@...r.kernel.org, Dave Chinner <david@...morbit.com>,
Jens Axboe <axboe@...nel.dk>, linux-fsdevel@...ck.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Christoph Hellwig <hch@....de>, linux-fsdevel@...r.kernel.org
Subject: Re: [RFC PATCH 1/4] splice: Fix corruption of spliced data after splice() returns
Linus Torvalds <torvalds@...ux-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?
David
Powered by blists - more mailing lists