linux-kernel - Re: support splice reads on seq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAHk-=wjvkBYOq0-xRH1YGXn4imB2iDVN1wEZisMcQd7dPeNbuw@mail.gmail.com>
Date:   Tue, 3 Nov 2020 11:07:30 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Christoph Hellwig <hch@....de>
Cc:     Al Viro <viro@...iv.linux.org.uk>,
        Greg KH <gregkh@...uxfoundation.org>,
        Alexey Dobriyan <adobriyan@...il.com>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: support splice reads on seq_file based procfs files

On Tue, Nov 3, 2020 at 11:02 AM Christoph Hellwig <hch@....de> wrote:
>
> > 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

Yeah, that would be covered by that proc_single_ops case.

Those four cases should really handle all of the normal /proc seq ops.
Anything else is going to be something very special.

               Linus