seccomp_bpf.c:2880:global.get_metadata:Expected 0 (0) == seccomp(1, 2, &prog) (4294967295)
Michael Ellerman
mpe at ellerman.id.au
Wed May 9 00:34:03 AEST 2018
Mathieu Malaterre <malat at debian.org> 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
More information about the Linuxppc-dev
mailing list