[Bug 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc

[Łukasz Zemczak]

Hello Dan, or anyone else affected,

Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.3 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: systemd (Ubuntu Groovy)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1918696

Title:
  libseccomp 2.5.1 will break unit tests on ppc

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [impact]

  when libseccomp is upgraded to 2.5.1 on all releases, the systemd
  seccomp unit tests will start failing on ppc, as
  RestrictAddressFamilies= will no longer work on that arch.

  However, the systemd.exec man page has stated that
  RestrictAddressFamiles= doesn't work on ppc since before bionic.

  [test case]

  check systemd autopkgtest on ppc, looking at the
  test_restrict_access_familes unit test

  [regression potential]

  any regression would involve the use of RestrictAddressFamilies=,
  either no longer restricting or incorrectly restricting address
  familes.

  [scope]

  this is needed for b/f/g

  this was fixed upstream by commit
  d5923e38bc0e6cf9d7620ed5f1f8606fe7fe1168 which is included in 247, so
  this is fixed in h already

  This isn't needed in x, because it doesn't include upstream commit
  469830d1426a91e0897c321fdc8ee428f0a750c1 which reworked the code to
  switch from seccomp_rule_add to seccomp_rule_add_exact, so systemd
  could handle lack of arch support itself, instead of allowing the 'not
  exact' seccomp syscall to just ignore the call due to lack of arch
  support.

  [other info]

  libseccomp will be updated to 2.5.1 in the near future so this is
  needed before that update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696/+subscriptions