From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0132.outbound.protection.outlook.com [157.56.110.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id A49A41A2B48 for ; Mon, 23 Mar 2015 22:45:08 +1100 (AEDT) Message-ID: <550FFCAB.8080409@freescale.com> Date: Mon, 23 Mar 2015 13:44:43 +0200 From: Purcareata Bogdan MIME-Version: 1.0 To: Benjamin Herrenschmidt , Michael Ellerman Subject: Re: [PATCH v4 0/3] powerpc: Enable seccomp filter support References: <1424247413-20753-1-git-send-email-bogdan.purcareata@freescale.com> <54F01C85.2020602@freescale.com> <1425070490.4645.86.camel@kernel.crashing.org> In-Reply-To: <1425070490.4645.86.camel@kernel.crashing.org> Content-Type: text/plain; charset="utf-8"; format=flowed Cc: linux-kernel@vger.kernel.org, pmoore@redhat.com, paulus@samba.org, Bogdan Purcareata , Scott Wood , linuxppc-dev@lists.ozlabs.org, strosake@linux.vnet.ibm.com List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 27.02.2015 22:54, Benjamin Herrenschmidt wrote: > On Fri, 2015-02-27 at 09:28 +0200, Purcareata Bogdan wrote: >> Ping? > > What is the ping for ? > > Ben. Hello Ben, I just wanted to check with you what's the current status of these patches. I noticed in patchwork [1][2][3] that the patches are marked as non-applicable. As of today, I cloned Michael Ellerman's tree [4], applied the patches on the master branch, compiled and tested. Tests pass both with the libseccomp regression suite and my LXC tests. Is there a specific tree I should send them against, or on another mailing list? Is there any other reason the patches are not applicable? [1] https://patchwork.ozlabs.org/patch/440827/ [2] https://patchwork.ozlabs.org/patch/440828/ [3] https://patchwork.ozlabs.org/patch/440829/ [4] git://git.kernel.org/pub/scm/linux/kernel/git/mpe/linux.git Thank you, Bogdan P. >> On 18.02.2015 10:16, Bogdan Purcareata wrote: >>> Add the missing pieces in order to enable SECCOMP_FILTER on PowerPC >>> architectures, and enable this support. >>> >>> Testing has been pursued using libseccomp with the latest ppc support patches >>> [1][2], on Freescale platforms for both ppc and ppc64. Support on ppc64le has >>> also been tested, courtesy of Mike Strosaker. >>> >>> [1] https://groups.google.com/forum/#!topic/libseccomp/oz42LfMDsxg >>> [2] https://groups.google.com/forum/#!topic/libseccomp/TQWfCt_nD7c >>> >>> v4: >>> - rebased on top of 3.19 >>> >>> v3: >>> - keep setting ENOSYS in syscall entry assembly when syscall tracing is disabled >>> >>> v2: >>> - move setting ENOSYS from syscall entry assembly to do_syscall_trace_enter >>> >>> Bogdan Purcareata (3): >>> powerpc: Don't force ENOSYS as error on syscall fail >>> powerpc: Relax secure computing on syscall entry trace >>> powerpc: Enable HAVE_ARCH_SECCOMP_FILTER >>> >>> arch/powerpc/Kconfig | 1 + >>> arch/powerpc/kernel/entry_32.S | 7 ++++++- >>> arch/powerpc/kernel/entry_64.S | 5 +++-- >>> arch/powerpc/kernel/ptrace.c | 8 ++++++-- >>> 4 files changed, 16 insertions(+), 5 deletions(-) >>> > >