From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: David Laight Subject: RE: [PATCH] Adds a new ioctl32 syscall for backwards compatibility layers Date: Sun, 17 Jan 2021 18:31:36 +0000 Message-ID: References: <20210106064807.253112-1-Sonicadvance1@gmail.com> <20210116090721.GA30277@lst.de> In-Reply-To: <20210116090721.GA30277@lst.de> MIME-Version: 1.0 Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT List-ID: To: 'Christoph Hellwig' , Andy Lutomirski Cc: Arnd Bergmann , Ryan Houdek , Catalin Marinas , Will Deacon , Alexander Viro , Arnd Bergmann , Christian Brauner , Andrew Morton , Minchan Kim , Aleksa Sarai , Sargun Dhillon , Miklos Szeredi , Vincenzo Frascino , Amanieu d'Antras , Willem de Bruijn , YueHaibing , Xiaoming Ni , Heiko Carstens , "Eric W. Biederman" , Joe Perches , Jan Kara , David Rientjes , Arnaldo Carvalho de Melo , "David S. Miller" , Linux ARM , "linux-kernel@vger.kernel.org" , Linux FS-devel Mailing List , Linux API , linux-arch From: Christoph Hellwig > Sent: 16 January 2021 09:07 ... > > I personally would like to see in_compat_syscall() go away, > > but some other people (Hi, Christoph!) disagree, and usage seems to be > > increasing, not decreasing. > > I'm absolutely against it going away. in_compat_syscall helped to > remove so much crap compared to the explicit compat syscalls. The only other real option is to pass the 'syscall type' explicitly through all the layers into every piece of code that might need it. So passing it as a 'parameter' that is (probably) current->syscall_type does make sense. It might even make sense have separate bits for the required emulations. So you'd have separate bits for '32bit pointers' and '64bit items 32bit aligned' (etc). David - Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)