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
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.

  backport time64 syscalls whitelist

Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Bionic:
Status in libseccomp source package in Disco:
  Won't Fix
Status in libseccomp source package in Eoan:
Status in libseccomp source package in Focal:
  Fix Released

Bug description:
  A number of new *time64 syscalls are introduced in newer kernel series

  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 

  See a similar report at Fedora:

  A solution could be to backport the related changes from 2.4.2
  similarly to what happened for the statx whitelisting

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to