From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (bilbo.ozlabs.org [203.11.71.1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 40gMSH1FBVzDrnp for ; Wed, 9 May 2018 00:34:07 +1000 (AEST) From: Michael Ellerman To: Mathieu Malaterre , linuxppc-dev Subject: Re: seccomp_bpf.c:2880:global.get_metadata:Expected 0 (0) == seccomp(1, 2, &prog) (4294967295) In-Reply-To: References: Date: Wed, 09 May 2018 00:34:03 +1000 Message-ID: <874lji1ajo.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Mathieu Malaterre writes: > Hi there, > > Quick question (I have not investigate root cause): is support for > seccomp complete on ppc32 ? Doesn't look like it does it :) > $ make KBUILD_OUTPUT=/tmp/kselftest TARGETS=seccomp kselftest > ... > seccomp_bpf.c:1804:TRACE_syscall.ptrace_syscall_dropped:Expected 1 (1) > == syscall(286) (4294967295) > TRACE_syscall.ptrace_syscall_dropped: Test failed at step #13 > [ FAIL ] TRACE_syscall.ptrace_syscall_dropped > ... > [ RUN ] global.get_metadata > seccomp_bpf.c:2880:global.get_metadata:Expected 0 (0) == seccomp(1, 2, > &prog) (4294967295) > seccomp_bpf.c:2892:global.get_metadata:Expected 1 (1) == > read(pipefd[0], &buf, 1) (0) > global.get_metadata: Test terminated by assertion > [ FAIL ] global.get_metadata I'm not sure sorry. That could be a test case bug, hard to say without looking at the details. cheers