This is not a bug in systemd.
The problem is that libseccomp was patched at version
2.3.1-2.1ubuntu4.1, in d/p/lp-1815415-arch-update-syscalls-for-
Linux-4.9.patch, to add a definition for the pkey_mprotect syscall. The
systemd test case checks for the definition of this syscall, and uses it
if it's defined, which with the new libseccomp library, it is.
However, the ppc64el kernel doesn't add support for the pkey_mprotect
syscall until 4.16.
Either the bionic 4.15 kernel should add support for pkey_mprotect
syscall (commit 3350eb2ea127978319ced883523d828046af4045, at least,
possibly more), or libseccomp should remove it, at least for ppc64el
builds on bionic. Adding support for it to the kernel for ppc64el is
probably the best approach.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => Invalid
** Also affects: libseccomp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: libseccomp (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821625
Title:
systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
seccomp)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
