* Marc Hartmayer (mhart...@linux.ibm.com) wrote:
> The virtiofsd currently crashes on s390x. This is because of a
> `sigreturn` system call. See audit log below:
>
> type=SECCOMP msg=audit(1669382477.611:459): auid=4294967295 uid=0 gid=0
> ses=4294967295 subj=system_u:system_r:virtd_t:s0-s0:c0.c1023 pid=6649
> comm="virtiofsd" exe="/usr/libexec/virtiofsd" sig=31 arch=80000016
> syscall=119 compat=0 ip=0x3fff15f748a code=0x80000000AUID="unset" UID="root"
> GID="root" ARCH=s390x SYSCALL=sigreturn
I'm curious; doesn't that mean that some signal is being delivered and
you're returning? Which one?
Dave
> Signed-off-by: Marc Hartmayer <mhart...@linux.ibm.com>
> ---
> tools/virtiofsd/passthrough_seccomp.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/virtiofsd/passthrough_seccomp.c
> b/tools/virtiofsd/passthrough_seccomp.c
> index 888295c073de..0033dab4939e 100644
> --- a/tools/virtiofsd/passthrough_seccomp.c
> +++ b/tools/virtiofsd/passthrough_seccomp.c
> @@ -110,6 +110,7 @@ static const int syscall_allowlist[] = {
> #endif
> SCMP_SYS(set_robust_list),
> SCMP_SYS(setxattr),
> + SCMP_SYS(sigreturn),
> SCMP_SYS(symlinkat),
> SCMP_SYS(syncfs),
> SCMP_SYS(time), /* Rarely needed, except on static builds */
> --
> 2.34.1
>
--
Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
