From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 51D26C388F2 for ; Tue, 3 Nov 2020 19:03:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0DD7022226 for ; Tue, 3 Nov 2020 19:03:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729394AbgKCTC5 (ORCPT ); Tue, 3 Nov 2020 14:02:57 -0500 Received: from verein.lst.de ([213.95.11.211]:38744 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727688AbgKCTC5 (ORCPT ); Tue, 3 Nov 2020 14:02:57 -0500 Received: by verein.lst.de (Postfix, from userid 2407) id 1CB3C6736F; Tue, 3 Nov 2020 20:02:54 +0100 (CET) Date: Tue, 3 Nov 2020 20:02:53 +0100 From: Christoph Hellwig To: Linus Torvalds Cc: Christoph Hellwig , Al Viro , Greg KH , Alexey Dobriyan , linux-fsdevel , Linux Kernel Mailing List Subject: Re: support splice reads on seq_file based procfs files Message-ID: <20201103190253.GA24382@lst.de> References: <20201029100950.46668-1-hch@lst.de> <20201103184815.GA24136@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Tue, Nov 03, 2020 at 10:57:10AM -0800, Linus Torvalds wrote: > On Tue, Nov 3, 2020 at 10:48 AM Christoph Hellwig wrote: > > > > ping? > > It looked fine by me, although honestly, I'd prefer that last patch to > be the minimum possible if we want this for 5.10. > > Yeah, that might technically be just cpuinfo, but I'd be ok with the > other read-only core proc files (ie I would *not* add it to anything > that has a .proc_write operation like the ones in proc_net.c). > > IOW, I'd start with just cpuinfo_proc_ops, proc_seq_ops, > proc_single_ops, and stat_proc_ops. I think Greg reported another test case hitting /proc/version > > Because honestly, I'd rather restrict splice() as much as possible > than try to say "everything should be able to do splice". sure.