Unfortunately this requested change has introduced severe issues with the kernels in which it was applied, by breaking compatibility with the 32bit glibc.
Even if an application is built with _TIME_BITS=64, and therefore the application has no year 2038 issues, glibc itself will use the 32bit time syscalls when there is no deadline or when the deadline fits in the 32bit syscall.
Unfortunately this requested change has introduced severe issues with the kernels in which it was applied, by breaking compatibility with the 32bit glibc.
Even if an application is built with _TIME_BITS=64, and therefore the application has no year 2038 issues, glibc itself will use the 32bit time syscalls when there is no deadline or when the deadline fits in the 32bit syscall.
See, apart from the issue linked above, these which provide more details: /bugs.launchpad .net/ubuntu/ +source/ linux-azure/ +bug/2071445 /github. com/actions/ runner- images/ issues/ 9977
https:/
https:/
Please note that it is quite normal to build and run 32bit applications in 64bit systems, and that it is the base for a lot of CI/test setups.