[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200628072012.GA16344@lst.de>
Date: Sun, 28 Jun 2020 09:20:12 +0200
From: Christoph Hellwig <hch@....de>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Christoph Hellwig <hch@....de>, 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 Sat, Jun 27, 2020 at 03:15:00PM -0700, Linus Torvalds 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.
Thanks. If we move forward with this I'd like to get it merge soon
so that we get an as long as possible exposure in linux-next to find
the occasional candidate that needs to be converted to the iter ops.
Powered by blists - more mailing lists