From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman) Subject: Re: [PATCH 1/8] signal/alpha: Document a conflict with SI_USER for SIGTRAP Date: Tue, 18 Jul 2017 08:37:36 -0500 Message-ID: <87fudthnmn.fsf@xmission.com> References: <87efu22set.fsf@xmission.com> <20170630123906.8865-1-ebiederm@xmission.com> <20170702141320.GA32254@ls3530.fritz.box> <87fudz5lol.fsf@xmission.com> <20170717081438.rdbwspz25bn6oz7h@tower> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20170717081438.rdbwspz25bn6oz7h@tower> (Michael Cree's message of "Mon, 17 Jul 2017 20:14:38 +1200") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Michael Cree Cc: Andrei Vagin , Greg KH , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Pavel Emelyanov , linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Helge Deller , Michael Kerrisk , Matt Turner , Ivan Kokshaysky , Al Viro , Andy Lutomirski , Cyrill Gorcunov , Thomas Gleixner , Richard Henderson , Andrey Vagin , linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Linux Containers , Oleg Nesterov , linux-alpha-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Linus Torvalds , Willy Tarreau List-Id: linux-arch.vger.kernel.org Michael Cree writes: > On Fri, Jul 14, 2017 at 05:59:06AM -0500, Eric W. Biederman wrote: >> in which cases the oddities will happen let alone test them. Plus at >> least for ia64 and alpha those architectures don't appear to be >> receiving updates for new syscalls, and no new hardware is being built >> so I don't know how much longer they will last. >> >> That is building for alpha gives: >> > CALL /home/eric/projects/linux/linux-exit-cleanups/scripts/checksyscalls.sh >> > :1239:2: warning: #warning syscall seccomp not implemented [-Wcpp] >> > :1248:2: warning: #warning syscall bpf not implemented [-Wcpp] >> > :1299:2: warning: #warning syscall userfaultfd not implemented [-Wcpp] >> > :1302:2: warning: #warning syscall membarrier not implemented [-Wcpp] >> > :1305:2: warning: #warning syscall mlock2 not implemented [-Wcpp] >> > :1308:2: warning: #warning syscall copy_file_range not implemented [-Wcpp] >> > :1311:2: warning: #warning syscall preadv2 not implemented [-Wcpp] >> > :1314:2: warning: #warning syscall pwritev2 not implemented [-Wcpp] >> > :1317:2: warning: #warning syscall pkey_mprotect not implemented [-Wcpp] >> > :1320:2: warning: #warning syscall pkey_alloc not implemented [-Wcpp] >> > :1323:2: warning: #warning syscall pkey_free not implemented [-Wcpp] >> > :1326:2: warning: #warning syscall statx not implemented [-Wcpp] > > Patches to wire up most of those syscalls on Alpha was posted recently > along with others to fix module loading, etc., but unfortunately they > do not appear to have been applied during the merge window... Odd. In general wiring up system calls is something that can even happen in -rc2 or -rc3 as system calls get added in -rc1 and then the architectures have a chance to send in the small patches wiring the up. At least that is how I understand the usual rules for being a non-x86 architecture. Eric From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out01.mta.xmission.com ([166.70.13.231]:41381 "EHLO out01.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751399AbdGRNpo (ORCPT ); Tue, 18 Jul 2017 09:45:44 -0400 From: ebiederm@xmission.com (Eric W. Biederman) References: <87efu22set.fsf@xmission.com> <20170630123906.8865-1-ebiederm@xmission.com> <20170702141320.GA32254@ls3530.fritz.box> <87fudz5lol.fsf@xmission.com> <20170717081438.rdbwspz25bn6oz7h@tower> Date: Tue, 18 Jul 2017 08:37:36 -0500 In-Reply-To: <20170717081438.rdbwspz25bn6oz7h@tower> (Michael Cree's message of "Mon, 17 Jul 2017 20:14:38 +1200") Message-ID: <87fudthnmn.fsf@xmission.com> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [PATCH 1/8] signal/alpha: Document a conflict with SI_USER for SIGTRAP Sender: linux-arch-owner@vger.kernel.org List-ID: To: Michael Cree Cc: Helge Deller , linux-kernel@vger.kernel.org, Andy Lutomirski , Linus Torvalds , Al Viro , Oleg Nesterov , Andrei Vagin , Thomas Gleixner , Greg KH , Andrey Vagin , Serge Hallyn , Pavel Emelyanov , Cyrill Gorcunov , Peter Zijlstra , Willy Tarreau , linux-arch@vger.kernel.org, linux-api@vger.kernel.org, Linux Containers , Michael Kerrisk , Richard Henderson , Ivan Kokshaysky , Matt Turner , linux-alpha@vger.kernel.org Message-ID: <20170718133736.ZqCyE6WElVXf8HdJMzZV-EZhxLHkAZa7c3Lo8E_w_gU@z> Michael Cree writes: > On Fri, Jul 14, 2017 at 05:59:06AM -0500, Eric W. Biederman wrote: >> in which cases the oddities will happen let alone test them. Plus at >> least for ia64 and alpha those architectures don't appear to be >> receiving updates for new syscalls, and no new hardware is being built >> so I don't know how much longer they will last. >> >> That is building for alpha gives: >> > CALL /home/eric/projects/linux/linux-exit-cleanups/scripts/checksyscalls.sh >> > :1239:2: warning: #warning syscall seccomp not implemented [-Wcpp] >> > :1248:2: warning: #warning syscall bpf not implemented [-Wcpp] >> > :1299:2: warning: #warning syscall userfaultfd not implemented [-Wcpp] >> > :1302:2: warning: #warning syscall membarrier not implemented [-Wcpp] >> > :1305:2: warning: #warning syscall mlock2 not implemented [-Wcpp] >> > :1308:2: warning: #warning syscall copy_file_range not implemented [-Wcpp] >> > :1311:2: warning: #warning syscall preadv2 not implemented [-Wcpp] >> > :1314:2: warning: #warning syscall pwritev2 not implemented [-Wcpp] >> > :1317:2: warning: #warning syscall pkey_mprotect not implemented [-Wcpp] >> > :1320:2: warning: #warning syscall pkey_alloc not implemented [-Wcpp] >> > :1323:2: warning: #warning syscall pkey_free not implemented [-Wcpp] >> > :1326:2: warning: #warning syscall statx not implemented [-Wcpp] > > Patches to wire up most of those syscalls on Alpha was posted recently > along with others to fix module loading, etc., but unfortunately they > do not appear to have been applied during the merge window... Odd. In general wiring up system calls is something that can even happen in -rc2 or -rc3 as system calls get added in -rc1 and then the architectures have a chance to send in the small patches wiring the up. At least that is how I understand the usual rules for being a non-x86 architecture. Eric