Subject: bug#47708: 28.0.50; SIGSYS test failure with seccomp-filter.bpf

From: Philipp Stephani <[email-masked]>
Date: Sun, 11 Apr 2021 15:58:57 +0200

Am So., 11. Apr. 2021 um 15:19 Uhr schrieb Basil L. Contovounesios
<[email-masked]>:
>
> On Debian Testing with libseccomp 2.5.1-1, 'make test/emacs-tests' fails
> with:
>
>   Test emacs-tests/seccomp/allows-stdout backtrace:
>     signal(ert-test-failed (((should (eql status 0)) :form (eql "Bad sys
>     ert-fail(((should (eql status 0)) :form (eql "Bad system call" 0) :v
>     [...]
>     normal-top-level()
>   Test emacs-tests/seccomp/allows-stdout condition:
>       Info: Process output:
>       (ert-test-failed
>        ((should
>          (eql status 0))
>         :form
>         (eql "Bad system call" 0)
>         :value nil))
>      FAILED  2/6  emacs-tests/seccomp/allows-stdout (0.032159 sec)
>

Thanks for the report! Could you check which syscall exactly is
failing, e.g. using
journalctl -g SECCOMP -t audisp-syslog
(assuming that system uses systemd and seccomp audit logging is enabled).