[Bug 1868720] Re: backport time64 syscalls whitelist
*** This bug is a duplicate of bug 1876055 *** https://bugs.launchpad.net/bugs/1876055 Thanks Jamie, that will fix this bug here as well then, IMHO we should mark it as a dup then. ** This bug has been marked a duplicate of bug 1876055 SRU: Backport 2.4.3-1ubuntu2 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64 syscalls whitelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1868720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868720] Re: backport time64 syscalls whitelist
There is actually an SRU in progress for libseccomp: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64 syscalls whitelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1868720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868720] Re: backport time64 syscalls whitelist
** Also affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Changed in: docker.io (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64 syscalls whitelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1868720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868720] Re: backport time64 syscalls whitelist
Focal may be affected after all then -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64 syscalls whitelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1868720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868720] Re: backport time64 syscalls whitelist
turns ou we may also need this fix in docker: https://github.com/moby/moby/pull/40739 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64 syscalls whitelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1868720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868720] Re: backport time64 syscalls whitelist
of course, you do: cd /tmp && git clone https://github.com/xantares/test-seccomp-time64.git && docker build test-seccomp-time64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64 syscalls whitelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1868720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868720] Re: backport time64 syscalls whitelist
Could you provide a failing test case so we can base the SRU (stable release update) on that use it as a non-regression test ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64 syscalls whitelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1868720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868720] Re: backport time64 syscalls whitelist
I believe the patch you're mentioning is worth backporting to Bionic and Eoan is this: $ git log -1 -p be65b26b67099be2b2b4890d736dbd1ad15adf36 | diffstat include/seccomp-syscalls.h| 208 +- src/arch-aarch64-syscalls.c | 35 ++- src/arch-arm-syscalls.c | 35 ++- src/arch-mips-syscalls.c | 51 -- src/arch-mips64-syscalls.c| 31 ++ src/arch-mips64n32-syscalls.c | 31 ++ src/arch-parisc-syscalls.c| 33 ++ src/arch-ppc-syscalls.c | 51 -- src/arch-ppc64-syscalls.c | 53 -- src/arch-s390-syscalls.c | 57 --- src/arch-s390.c | 160 src/arch-s390x-syscalls.c | 59 --- src/arch-s390x.c | 160 src/arch-x32-syscalls.c | 31 ++ src/arch-x86-syscalls.c | 105 ++--- src/arch-x86.c| 161 src/arch-x86_64-syscalls.c| 31 ++ 17 files changed, 1150 insertions(+), 142 deletions(-) and to be honest that seems appropriate as it only updates the tables and allows supporting newer system calls for all arches. ** Changed in: libseccomp (Ubuntu) Status: New => Triaged ** Also affects: libseccomp (Ubuntu Focal) Importance: Undecided Status: Triaged ** Also affects: libseccomp (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: libseccomp (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libseccomp (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: libseccomp (Ubuntu Focal) Status: Triaged => Fix Released ** Changed in: libseccomp (Ubuntu Eoan) Status: New => Confirmed ** Changed in: libseccomp (Ubuntu Disco) Status: New => Won't Fix ** Changed in: libseccomp (Ubuntu Bionic) Status: New => Confirmed ** Tags added: server-next ** Changed in: libseccomp (Ubuntu Bionic) Status: Confirmed => Triaged ** Changed in: libseccomp (Ubuntu Eoan) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64 syscalls whitelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1868720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868720] Re: backport time64 syscalls whitelist
The attachment "backport time64 syscalls from 2.4.2 into 2.4.1" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64 syscalls whitelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1868720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868720] Re: backport time64 syscalls whitelist
** Patch added: "backport time64 syscalls from 2.4.2 into 2.4.1" https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1868720/+attachment/5340882/+files/libseccomp241-time64.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64 syscalls whitelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1868720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
