Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757597AbbLBLEx (ORCPT ); Wed, 2 Dec 2015 06:04:53 -0500 Received: from mout.kundenserver.de ([212.227.126.187]:64281 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755220AbbLBLEv (ORCPT ); Wed, 2 Dec 2015 06:04:51 -0500 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Yury Norov , pinskia@gmail.com, Prasun.Kapoor@caviumnetworks.com, catalin.marinas@arm.com, Nathan_Lynch@mentor.com, linux-kernel@vger.kernel.org, agraf@suse.de, klimov.linux@gmail.com, broonie@kernel.org, jan.dakinevich@gmail.com, joseph@codesourcery.com, ddaney.cavm@gmail.com, schwab@suse.de, bamvor.zhangjian@huawei.com, philipp.tomsich@theobroma-systems.com, andrey.konovalov@linaro.org, christoph.muellner@theobroma-systems.com Subject: Re: [PATCH v6 14/19] arm64:ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it Date: Wed, 02 Dec 2015 12:03:54 +0100 Message-ID: <5594882.0HTLvCyrNc@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <20151202100153.GA21461@yury-N73SV> References: <1447795019-30176-1-git-send-email-ynorov@caviumnetworks.com> <3754277.KmO9Nk3XLD@wuerfel> <20151202100153.GA21461@yury-N73SV> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:IWlO6+XMbM8QA2TuXn8gK2WiniNKhD5KYEdOPE+c1pWPWOZfHb0 wz29q4zayF78oyeSV4QmTcSOKfqdH9/maPMZy2FjtnPX2aUie33W3AgGyT+x7tspqwHNnUS dEd2fpsMI3F1v8C/Jcw2zjIvx5ardoNSJncy4UaYGLALBxMBiIFyptte+Pb5fkI15ndupp0 d5xWCBEbWyhSppSNUuLng== X-UI-Out-Filterresults: notjunk:1;V01:K0:tUJ3qFi5oJ8=:Sle+U6aeX28j6+kbJnzxeV EUeo+TDaKpeikwoPgJMRhKKoqWIidz6dNYHQ+MzWMXismWw16CAEkh6l1XvCCS3CK2MxW8qiB IJ98GmzMvXmN7rLbXCq21OrmepdRwab/P78B1aWtLo9wVHhi4gXfJ1LS0iE8XxZ+CGrtiFWkv 5IqfYewnB+mMmD0chGQDY4IphIYYqzZENGn2sk5aGtudQiDIhNpsbe5hbPwh8PiGAStQkVmCR WjH+WjbV/MNznCPnMOqvQ18qMr3JZqIXAVgoluEIiClLUsuyusZ7CeYPuOa4187b/mqVqmU9J +N1i4KFPMSzLyW+ZMn7Hb3Nh4iDeEzpsIhGuTqTub9rkAeIL9gQLWIZ7ik+4ugV3EKBBrpF9O W7HOrZTCYNyjoT8UhMtqUn5gDhdOkoAkhXpb8tvFuyjbSOy8fpOlwJbih244SN1+PmbE/occh OrgE9OnO/IJ2MNolEoxFTVzJpBsR6dqyX/JVuKmOrxbMX4JQlXYPlz4cg7gFwfDRx/+g2ARFX eSKorZbUsAN8BDhUj+YZjFWn8cihjw/vqYeTI/q70x9h8ut9SpDMl+24G+MN0IyYudqv2Y5/2 WeO5XgCSya7KeivC11x4WZlO776E9JFBPKx9x4qsmFMrfmhITglpu3TLYyiW+cwsfMyoXe4Qy zHtbgHMSUkEnTKZk/giMPo61TKHNvYkC7vQ82LJn7bsQg8g3GFISk3dqR5TeiudIxY6HblveV jCHrLnrPWR+KSCra Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1591 Lines: 42 On Wednesday 02 December 2015 13:01:53 Yury Norov wrote: > On Tue, Nov 17, 2015 at 10:57:52PM +0100, Arnd Bergmann wrote: > > It looks, all them are needed. > > > > +asmlinkage long compat_sys_mmap2_wrapper(void); > > > +#define sys_mmap2 compat_sys_mmap2_wrapper > > This wrapper checks alignement of pgoff, if page sise is greater than > 4K Ok. > > > +asmlinkage long compat_sys_fstatfs64_wrapper(void); > > > +#define compat_sys_fstatfs64 compat_sys_fstatfs64_wrapper > > > +asmlinkage long compat_sys_statfs64_wrapper(void); > > > +#define compat_sys_statfs64 compat_sys_statfs64_wrapper > > This two hacks fix an alignment issue. I didn't check all details but > it looks like sizeof(compat_statfs64) is different in kernel and library. > And this size is passed as 2nd argument to compat syscalls. We can > handle it in userspace but I don't see any advantage. Ah, so it's a hack for OABI compatibility. I wonder if we can just drop the wrapper and the ARCH_PACK_COMPAT_STATFS64 definition on arm64 as we don't handle OABI user space anyway. Maybe it's too risky, when there is someone that added the packing in user space on EABI after all. > All this handlers are shared between ilp32 and aarch32. > This is best we came up, as it doesn't add new hacks, but reuses old > ones... Ok. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/