-
Especially 4.19 is not 2038 safe and 32 bit kernels do not have CONFIG_64BIT_TIME set, which ends up in __kernel_timespec being defined in a non y2038 safe way. cobalt_get_timespec64 will copy the upper bytes of the sec field into the nsec field, which is always zero. Testing y2038 syscalls on a non y2038 safe kernel doesn't make sense, hence limiting the test runs to kernels with 2038 support. Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
8a2f250d