** 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
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1868720
Title:
backport time64 syscalls whitelist
Status in docker.io package in Ubuntu:
New
Status in libseccomp package in Ubuntu:
Fix Released
Status in docker.io source package in Bionic:
New
Status in libseccomp source package in Bionic:
Triaged
Status in docker.io source package in Disco:
Won't Fix
Status in libseccomp source package in Disco:
Won't Fix
Status in docker.io source package in Eoan:
New
Status in libseccomp source package in Eoan:
Triaged
Status in docker.io source package in Focal:
New
Status in libseccomp source package in Focal:
Fix Released
Bug description:
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: timerfd_settime64
412: utimensat_time64
413: pselect6_time64
414: ppoll_time64
In particular utimensat_time64 is now used inside glibc>=2.31
In turn ubuntu with has trouble running docker images of newer distros.
This problem affects libseccomp<2.4.2, ie bionic (lts), and eoan, but not
focal.
See a similar report at Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1770154
A solution could be to backport the related changes from 2.4.2
similarly to what happened for the statx whitelisting
(https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1868720/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp