[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yg77bNZfNhSk0bVQ@zeniv-ca.linux.org.uk>
Date: Fri, 18 Feb 2022 01:50:36 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: Christophe Leroy <christophe.leroy@...roup.eu>
Cc: Arnd Bergmann <arnd@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Christoph Hellwig <hch@....de>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>,
"arnd@...db.de" <arnd@...db.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mark.rutland@....com" <mark.rutland@....com>,
"dalias@...c.org" <dalias@...c.org>,
"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
"linux-sh@...r.kernel.org" <linux-sh@...r.kernel.org>,
"peterz@...radead.org" <peterz@...radead.org>,
"jcmvbkbc@...il.com" <jcmvbkbc@...il.com>,
"guoren@...nel.org" <guoren@...nel.org>,
"sparclinux@...r.kernel.org" <sparclinux@...r.kernel.org>,
"linux-hexagon@...r.kernel.org" <linux-hexagon@...r.kernel.org>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
"will@...nel.org" <will@...nel.org>,
"ardb@...nel.org" <ardb@...nel.org>,
"linux-s390@...r.kernel.org" <linux-s390@...r.kernel.org>,
"bcain@...eaurora.org" <bcain@...eaurora.org>,
"deller@....de" <deller@....de>, "x86@...nel.org" <x86@...nel.org>,
"linux@...linux.org.uk" <linux@...linux.org.uk>,
"linux-csky@...r.kernel.org" <linux-csky@...r.kernel.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"geert@...ux-m68k.org" <geert@...ux-m68k.org>,
"linux-snps-arc@...ts.infradead.org"
<linux-snps-arc@...ts.infradead.org>,
"linux-xtensa@...ux-xtensa.org" <linux-xtensa@...ux-xtensa.org>,
"hca@...ux.ibm.com" <hca@...ux.ibm.com>,
"linux-alpha@...r.kernel.org" <linux-alpha@...r.kernel.org>,
"linux-um@...ts.infradead.org" <linux-um@...ts.infradead.org>,
"linux-m68k@...ts.linux-m68k.org" <linux-m68k@...ts.linux-m68k.org>,
"openrisc@...ts.librecores.org" <openrisc@...ts.librecores.org>,
"green.hu@...il.com" <green.hu@...il.com>,
"shorne@...il.com" <shorne@...il.com>,
"monstr@...str.eu" <monstr@...str.eu>,
"tsbogend@...ha.franken.de" <tsbogend@...ha.franken.de>,
"linux-parisc@...r.kernel.org" <linux-parisc@...r.kernel.org>,
"nickhu@...estech.com" <nickhu@...estech.com>,
"linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>,
"dinguyen@...nel.org" <dinguyen@...nel.org>,
"ebiederm@...ssion.com" <ebiederm@...ssion.com>,
"richard@....at" <richard@....at>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"davem@...emloft.net" <davem@...emloft.net>
Subject: Re: [PATCH v2 00/18] clean up asm/uaccess.h, kill set_fs for good
On Thu, Feb 17, 2022 at 07:20:11AM +0000, Christophe Leroy wrote:
> And we have also
> user_access_begin()/user_read_access_begin()/user_write_access_begin()
> which call access_ok() then do the real work. Could be made generic with
> call to some arch specific __user_access_begin() and friends after the
> access_ok() and eventually the might_fault().
Not a good idea, considering the fact that we do not want to invite
uses of "faster" variants...
Powered by blists - more mailing lists