LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Mathieu Malaterre <malat@debian.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: seccomp_bpf.c:2880:global.get_metadata:Expected 0 (0) == seccomp(1, 2, &prog) (4294967295)
Date: Wed, 09 May 2018 00:34:03 +1000	[thread overview]
Message-ID: <874lji1ajo.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <CA+7wUsxwRi3tLRR_+-=h_y2Xj_RfJS58E0vpa8K1KPtRAQpr_g@mail.gmail.com>

Mathieu Malaterre <malat@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

      reply	other threads:[~2018-05-08 14:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04  9:51 seccomp_bpf.c:2880:global.get_metadata:Expected 0 (0) == seccomp(1, 2, &prog) (4294967295) Mathieu Malaterre
2018-05-08 14:34 ` Michael Ellerman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874lji1ajo.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=malat@debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox