[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YeUjVZX764zLm9/K@infradead.org>
Date: Mon, 17 Jan 2022 00:05:41 -0800
From: Christoph Hellwig <hch@...radead.org>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Al Viro <viro@...iv.linux.org.uk>, linux-kernel@...r.kernel.org,
linux-arch@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Alexey Gladkov <legion@...nel.org>,
Kyle Huey <me@...ehuey.com>, Oleg Nesterov <oleg@...hat.com>,
Kees Cook <keescook@...omium.org>,
Heiko Carstens <hca@...ux.ibm.com>,
Vasily Gorbik <gor@...ux.ibm.com>,
Christian Borntraeger <borntraeger@...ibm.com>,
Alexander Gordeev <agordeev@...ux.ibm.com>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH 03/10] exit: Move oops specific logic from do_exit into
make_task_dead
On Fri, Jan 07, 2022 at 12:59:33PM -0600, Eric W. Biederman wrote:
> Assuming it won't be too much longer before the rest of the arches have
> set_fs/get_fs removed it looks like it makes sense to leave the
> force_uaccess_begin where it is, and just let force_uaccess_begin be
> removed when set_fs/get_fs are removed from the tree.
>
> Christoph does it look like the set_fs/get_fs removal work is going
> to stall indefinitely on some architectures? If so I think we want to
> find a way to get kernel threads to run with set_fs(USER_DS) on the
> stalled architectures. Otherwise I think we have a real hazard of
> introducing bugs that will only show up on the stalled architectures.
I really need help from the arch maintainers to finish the set_fs
removal. There have been very few arch maintainers helping with that
work (arm, arm64, parisc, m68k) in addition to the ones I did because
I have the test setups and knowledge. I'll send out another ping,
for necrotic architectures like ia64 and sh I have very little hope.
Powered by blists - more mailing lists