Submission type

• Bug report

systemd version the issue has been seen with

231

Used distribution

Debian

In case of bug report: Expected behaviour you didn't see

Successful boot on a systemd built with seccomp support but without kernel support (ie, CONFIG_SECCOMP unset).

In case of bug report: Unexpected behaviour you saw

Failure to boot as several services had SystemCallFilters applied in 231.

This was reported downstream. The debian kernels on arm* do not have SECCOMP enabled (not sure why), and this failure to boot as logind and journald fail to execute.

I think the fix would be to have an equivalent to mac_selinux_use for seccomp, and skip the setup in case it is not available.