Open The-King-of-Toasters opened 2 days ago
The result is a lot of breakage in our Linux wrappers, which makes me worried that the logic for determining the proper
timespec
to use was subtly broken all this time.
This situation is highly confusing because timespec
and kernel_timespec
are not the same thing, and the latter is usually what you want. But yes, the time stuff needs to be cleaned up and the standard library probably just wholesale switched to time64. (I can't think of a good reason why we would want to maintain time32 support?)
Kinda scary that the CI passed 🙃 - do we not test for time overflow?
Changes by Arnd Bergmann have migrated all supported architectures to use a table for their syscall lists. This removes the need of calling a C pre-processor and simplifies the logic dramatically. The side effect is the number of names changed on targets that use the "generic" table. That list (located under
scripts/syscall.tbl
) adds the_time64
suffix to syscalls taking atimespec64
on 32-bit targets. Similarly, the_time32
suffix has been removed.The result is a lot of breakage in our Linux wrappers, which makes me worried that the logic for determining the proper
timespec
to use was subtly broken all this time. Should be a good chance to finish #4726 - we only have 14 years after all...