support v5.4 syscalls
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| libseccomp (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Xenial |
New
|
Undecided
|
Unassigned | ||
| Bionic |
New
|
Undecided
|
Unassigned | ||
| Eoan |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
[Impact]
* update libssecomp syscalls, for example current seccomp on xenial and up, cannot correctly filter calls for focal armhf chroots on v5.4 kernels, due to new syscalls usage.
[Test Case]
* Boot v5.4 kernel
* Use seccomp to try to resolve new syscall numbers
* Rebuild snapd snap against bileto ppa with this change
* Test that this rebuild snapd snap, can correctly launch confined python armhf interpreter on arm64 v5.4 kernel (i.e. uc20 raspi arm64 beta image)
[Regression Potential]
* The issue only impacts when one is running on a newer / hwe kernel, and tries to seccomp filter newer binaries that use new syscalls. No changes are made to any existing syscalls or apis.
[Other Info]
* Bileto PPA with this change is being prepared with this change.
xenial: https:/
bionic: https:/
eoan: https:/
| Changed in libseccomp (Ubuntu): | |
| status: | New → Fix Released |
| description: | updated |
| Brian Murray (brian-murray) wrote | #1 |
| Changed in libseccomp (Ubuntu Eoan): | |
| status: | New → Won't Fix |
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release