Public bug reported:
[SRU Impact]
Sysctl was removed from 5.5 kernels. In src/test/test-seccomp.c,
test_protect_syscall
sysctl is called with the expectation the error result is EFAULT and not ENOSYS.
This affects autotests for all focal-5.15 linux kernels (hwe, azure, gcp, oem,
gke, oracle).
[Fix]
Assertion checks if either EFAULT or ENOSYS is returned. This way it will work
for focal-5.4 kernels and focal-5.15 kernels.
[Test to reproduce the issue]
1. Create a vm and install one of the focal-5.15 kernels (i.e
5.15.0-1029.35~20.04.1 linux-oracle-5.15).
2. Run the autotests for upstream and/or root-unittests:
autopkgtest --test-name=upstream systemd -- qemu <vm_image>
[Test to verify the fix]
1. Same as above
2. Apply the fix in your local repo and run the tests using your local repo
autopkgtest --test-name=upstream <path to systemd> -- qemu <vm_image>
[Where problems could occur]
This is not gonna affect end users since it is a change in the test only.
It may impact autotests, but it's a very low probability.
** Affects: systemd (Ubuntu)
Importance: Medium
Status: New
** Affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Merge proposal linked:
https://code.launchpad.net/~roxanan/ubuntu/+source/systemd/+git/systemd/+merge/436747
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
--
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/2004657
Title:
test_protect_syscall fails on focal-5.15 backports
Status in systemd package in Ubuntu:
New
Status in systemd source package in Focal:
New
Bug description:
[SRU Impact]
Sysctl was removed from 5.5 kernels. In src/test/test-seccomp.c,
test_protect_syscall
sysctl is called with the expectation the error result is EFAULT and not
ENOSYS.
This affects autotests for all focal-5.15 linux kernels (hwe, azure, gcp,
oem, gke, oracle).
[Fix]
Assertion checks if either EFAULT or ENOSYS is returned. This way it will
work for focal-5.4 kernels and focal-5.15 kernels.
[Test to reproduce the issue]
1. Create a vm and install one of the focal-5.15 kernels (i.e
5.15.0-1029.35~20.04.1 linux-oracle-5.15).
2. Run the autotests for upstream and/or root-unittests:
autopkgtest --test-name=upstream systemd -- qemu <vm_image>
[Test to verify the fix]
1. Same as above
2. Apply the fix in your local repo and run the tests using your local repo
autopkgtest --test-name=upstream <path to systemd> -- qemu <vm_image>
[Where problems could occur]
This is not gonna affect end users since it is a change in the test only.
It may impact autotests, but it's a very low probability.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2004657/+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
