[Touch-packages] [Bug 1868720] Re: backport time64 syscalls whitelist

2020-03-26 Thread xantares
Focal may be affected after all then -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64 syscalls whitelist Status in libseccomp package in

[Touch-packages] [Bug 1868720] Re: backport time64 syscalls whitelist

2020-03-26 Thread xantares
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 Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64

[Touch-packages] [Bug 1868720] Re: backport time64 syscalls whitelist

2020-03-25 Thread xantares
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 Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bu

[Touch-packages] [Bug 1868720] Re: backport time64 syscalls whitelist

2020-03-24 Thread xantares
** 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 Touch seeded packages, which is

[Touch-packages] [Bug 1868720] [NEW] backport time64 syscalls whitelist

2020-03-24 Thread xantares
Public bug reported: A number of new *time64 syscalls are introduced in newer kernel series (>=5.1.x): 403: clock_gettime64 404: clock_settime64 405: clock_adjtime64 406: clock_getres_time64 407: clock_nanosleep_time64 408: timer_gettime64 409: timer_settime64 410: timerfd_gettime64 411:

[Touch-packages] [Bug 1755250] Re: backport statx syscall whitelist fix

2019-03-08 Thread xantares
Has this been released ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1755250 Title: backport statx syscall whitelist fix Status in docker.io package in Ubuntu:

[Touch-packages] [Bug 1755250] Re: backport statx syscall whitelist fix

2019-02-28 Thread xantares
Ok for me too, I just installed libseccomp2_2.3.1-2.1ubuntu4.1_amd64.deb and it works: Step 16/18 : RUN gcc test-statx.c -o test-statx ---> Running in 501935bb923d Removing intermediate container 501935bb923d ---> a47f15cd6fc8 Step 17/18 : RUN touch test-file ---> Running in 1038f76ad915

[Touch-packages] [Bug 1755250] Re: backport statx syscall whitelist fix

2019-02-20 Thread xantares
hello, how long does it take usually for ubuntu to review the changes ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1755250 Title: backport statx syscall whitelist

[Touch-packages] [Bug 1755250] Re: backport statx syscall whitelist fix

2019-02-07 Thread xantares
here is a patch against libseccomp 2.3.1 in bionic (on top of the debian risc port patch) I manually applied changes from libseccomp 2.3.3 that reference the statx syscalls for the risc part i used the diff from