Hi,
On Tue, May 8, 2018 at 4:34 PM, Michael Ellerman [off-list ref] wrote:
Mathieu Malaterre [off-list ref] writes:
quoted
Hi there,
Quick question (I have not investigate root cause): is support for
seccomp complete on ppc32 ?
Doesn't look like it does it :)
quoted
$ 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.
I've reduced the test case to the attached file. Does that help, or
should I reduce it some more ?
$ gcc -m32 -o ptrace_syscall_dropped ptrace_syscall_dropped.c
running it as root:
# ./ptrace_syscall_dropped
[==========] Running 1 tests from 1 test cases.
[ RUN ] TRACE_syscall.ptrace_syscall_dropped
ptrace_syscall_dropped.c:298: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
[==========] 0 / 1 tests passed.
[ FAILED ]
Thanks