linux-kernel - Re: [RFC] stop using ->read and ->write for kernel access v2

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] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 27 Jun 2020 15:15:00 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Christoph Hellwig <hch@....de>
Cc:     Al Viro <viro@...iv.linux.org.uk>,
        Luis Chamberlain <mcgrof@...nel.org>,
        Matthew Wilcox <willy@...radead.org>,
        Kees Cook <keescook@...omium.org>,
        Iurii Zaikin <yzaikin@...gle.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [RFC] stop using ->read and ->write for kernel access v2

On Fri, Jun 26, 2020 at 12:58 AM Christoph Hellwig <hch@....de> wrote:
>
> as part of removing set_fs entirely (for which I have a working
> prototype), we need to stop calling ->read and ->write with kernel
> pointers under set_fs.
>
> My previous "clean up kernel_{read,write} & friends v5" series, on which
> this one builds, consolidate those calls into the __ḵernel_{read,write}
> helpers.  This series goes further and removes the option to call
> ->read and ->write with kernel pointers entirely.

Ack. I scanned through these and didn't find anything odd.

Which either means that it's all good, or that my scanning was too
limited. But this does feel like the right way to go about things.

Al?

                 Linus