Thread (58 messages) 58 messages, 11 authors, 2020-10-14

Re: remove the last set_fs() in common code, and remove it for x86 and powerpc v3

From: Al Viro <viro@zeniv.linux.org.uk>
Date: 2020-09-03 14:44:16
Also in: linux-arch, linux-fsdevel, lkml

On Thu, Sep 03, 2020 at 04:30:03PM +0200, Christoph Hellwig wrote:
On Thu, Sep 03, 2020 at 03:28:03PM +0100, Al Viro wrote:
quoted
On Thu, Sep 03, 2020 at 04:22:28PM +0200, Christoph Hellwig wrote:
quoted
Besides x86 and powerpc I plan to eventually convert all other
architectures, although this will be a slow process, starting with the
easier ones once the infrastructure is merged.  The process to convert
architectures is roughtly:

 (1) ensure there is no set_fs(KERNEL_DS) left in arch specific code
 (2) implement __get_kernel_nofault and __put_kernel_nofault
 (3) remove the arch specific address limitation functionality
The one to really watch out for is sparc; I have something in that
direction, will resurrect as soon as I'm done with eventpoll analysis...

I can live with this series; do you want that in vfs.git#for-next?
Either that or a separate tree is fine with me.  It would be good to
eventually have a non-rebased stable tree so that other arch trees
can work from it, though.
FWIW, vfs.git#for-next is always a merge of independent branches; I don't
put stuff directly into #for-next - too easy to lose that way.

IOW, that would be something like #base.set_fs, included into #for-next
merge set.  And I've no problem with never-rebased branches...

Where in the mainline are the most recent prereqs of this series?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help