** Description changed:

  [Impact]
  
-  * update libssecomp syscalls, for example current seccomp on xenial and
+  * 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
+  * 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)
+  * 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,
+  * 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.
+ 
+  * Bileto PPA with this change is being prepared with this change.
+ 
+ xenial: https://bileto.ubuntu.com/#/ticket/4041
+ bionic: https://bileto.ubuntu.com/#/ticket/4040
+ eoan: https://bileto.ubuntu.com/#/ticket/4039

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

Title:
  support v5.4 syscalls

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

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to