[Touch-packages] [Bug 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
This bug was fixed in the package systemd - 237-3ubuntu10.46 --- systemd (237-3ubuntu10.46) bionic; urgency=medium * d/p/lp1916485-Newer-Glibc-use-faccessat2-to-implement-faccessat.patch: Add support for faccessat2 (LP: #1916485) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b5f11a9baecf0cefb503632e938d473234172128 * d/p/lp1918696-shared-seccomp-util-address-family-filtering-is-brok.patch: Stop attempting to restrict address families on ppc archs (LP: #1918696) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4569a047ece8b1b300ef63e49b5aea8aba35c500 * d/p/lp1891810-seccomp-util-add-new-syscalls-from-kernel-5.6-to-sys.patch: Add openat2() syscall to seccomp filter list (LP: #1891810) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2ddfbfa79af4f22b7adf946c4299433fd74a4f17 -- Dan Streetman Wed, 17 Mar 2021 17:38:05 -0400 ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
This bug was fixed in the package systemd - 245.4-4ubuntu3.6 --- systemd (245.4-4ubuntu3.6) focal; urgency=medium * debian/patches/lp1916485-Newer-Glibc-use-faccessat2-to-implement-faccessat.patch: Add support for faccessat2 (LP: #1916485) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=affb2c6507dccfeed02820a2267639648e2a2260 * d/p/lp1918696-shared-seccomp-util-address-family-filtering-is-brok.patch: Stop attempting to restrict address families on ppc archs (LP: #1918696) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=daff4b6604362fcb5d305682216d5ca15a4c5738 * d/p/lp1891810-seccomp-util-add-new-syscalls-from-kernel-5.6-to-sys.patch: Add openat2() syscall to seccomp filter list (LP: #1891810) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=69c8a684e2513b2f6530e5a5cf15c83abfb7bc74 * d/p/lp1915887-Downgrade-a-couple-of-warnings-to-debug.patch: Downgrade some log messages so they stop spamming logs (LP: #1915887) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3c2c4731b90ed430ca1790270e69cd125643b94b * d/p/lp1887744-basic-unit-file-when-loading-linked-unit-files-use-l.patch: Use src name, not dst name, of symlinked unit files (LP: #1887744) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=03770601097cfdc09adeadf5593083da69345409 -- Dan Streetman Wed, 17 Mar 2021 17:36:08 -0400 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Committed Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
This bug was fixed in the package systemd - 246.6-1ubuntu1.3 --- systemd (246.6-1ubuntu1.3) groovy; urgency=medium * d/p/lp1918696-shared-seccomp-util-address-family-filtering-is-brok.patch: Stop attempting to restrict address families on ppc archs (LP: #1918696) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=34d1b2b4f4fdc349da37a07fe98418456167592a * d/p/lp1915887-Downgrade-a-couple-of-warnings-to-debug.patch: Downgrade some log messages so they stop spamming logs (LP: #1915887) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d092e70912009daf6f64182d86b3d92aed28722a * d/p/lp1887744-basic-unit-file-when-loading-linked-unit-files-use-l.patch: Use src name, not dst name, of symlinked unit files (LP: #1887744) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1e42633ccecc9c9157b19387c11ac1bf7ea7d161 -- Dan Streetman Wed, 10 Mar 2021 16:03:13 -0500 ** Changed in: systemd (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Committed Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
groovy: fail with systemd 246.6-1ubuntu1.2 and libseccomp/2.5.1-1ubuntu1~20.10.1 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/ppc64el/s/systemd/20210330_120842_8a4eb@/log.gz pass with systemd/246.6-1ubuntu1.3 libseccomp/2.5.1-1ubuntu1~20.10.1 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/ppc64el/s/systemd/20210401_180916_9d4c2@/log.gz ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Committed Status in systemd source package in Focal: Fix Committed 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
focal: fail with systemd 245.4-4ubuntu3.5 and libseccomp/2.5.1-1ubuntu1~20.04.1 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20210329_180851_bca64@/log.gz pass with systemd/245.4-4ubuntu3.6 and libseccomp/2.5.1-1ubuntu1~20.04.1 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20210401_173335_98ce7@/log.gz ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Committed Status in systemd source package in Focal: Fix Committed 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
bionic: fails with systemd 237-3ubuntu10.45 and libseccomp/2.5.1-1ubuntu1~18.04.1 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20210330_001358_e01e0@/log.gz pass with systemd/237-3ubuntu10.46 and libseccomp/2.5.1-1ubuntu1~18.04.1 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20210401_151939_a172a@/log.gz ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Committed Status in systemd source package in Focal: Fix Committed 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
Yes this is not needed for xenial since that version of systemd is not new enough to be affected by this issue (see the bug description for more details). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Committed Status in systemd source package in Focal: Fix Committed 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
What about xenial? Is xenial unaffected by this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Committed Status in systemd source package in Focal: Fix Committed 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
Hello Dan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.46 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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 Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Committed Status in systemd source package in Focal: Fix Committed 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
Hello Dan, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.6 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- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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 Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Committed 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
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 Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
** Description changed: [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 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: In Progress 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
