[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPnZJGCdr7pw80Pq38UacmxsbQAowmasPtFxQVCP+tm6Cj9pUg@mail.gmail.com>
Date: Tue, 26 Dec 2023 00:34:44 +0300
From: Askar Safin <safinaskar@...il.com>
To: Ahelenia Ziemiańska <nabijaczleweli@...ijaczleweli.xyz>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-man <linux-man@...r.kernel.org>, linux-s390@...r.kernel.org,
linux-serial@...r.kernel.org, netdev@...r.kernel.org,
virtualization@...ts.linux.dev
Subject: Re: Avoid unprivileged splice(file->)/(->socket) pipe exclusion
Hi, Ahelenia Ziemiańska! Thanks a lot for all this splice-related hard work!
In https://lore.kernel.org/lkml/CAHk-=wgG_2cmHgZwKjydi7=iimyHyN8aessnbM9XQ9ufbaUz9g@mail.gmail.com/
Linus said:
> I have grown to pretty much hate
> splice() over the years, just because it's been a constant source of
> sorrow in so many ways.
> It's just that it was never as lovely and as useful as it promised to
> be. So I'd actually be more than happy to just say "let's decommission
> splice entirely, just keeping the interfaces alive for backwards
> compatibility"
So probably we should do this as Linus suggested? I. e. fully remove
splice by replacing it with trivial read-write?
--
Askar Safin
Powered by blists - more mailing lists