Patchwork [5.1,119/122] y2038: Make CONFIG_64BIT_TIME unconditional

mail settings
Date May 23, 2019, 7:07 p.m.
Message ID <>
Download mbox | patch
Permalink /patch/32835/
State New
Headers show

Comments - May 23, 2019, 7:07 p.m.
From: Arnd Bergmann <>

commit f3d964673b2f1c5d5c68c77273efcf7103eed03b upstream.

As Stepan Golosunov points out, there is a small mistake in the
get_timespec64() function in the kernel. It was originally added under the
assumption that CONFIG_64BIT_TIME would get enabled on all 32-bit and
64-bit architectures, but when the conversion was done, it was only turned
on for 32-bit ones.

The effect is that the get_timespec64() function never clears the upper
half of the tv_nsec field for 32-bit tasks in compat mode. Clearing this is
required for POSIX compliant behavior of functions that pass a 'timespec'
structure with a 64-bit tv_sec and a 32-bit tv_nsec, plus uninitialized

The easiest fix for linux-5.1 is to just make the Kconfig symbol
unconditional, as it was originally intended. As a follow-up, the #ifdef
CONFIG_64BIT_TIME can be removed completely..

Note: for native 32-bit mode, no change is needed, this works as
designed and user space should never need to clear the upper 32
bits of the tv_nsec field, in or out of the kernel.

Fixes: 00bf25d693e7 ("y2038: use time32 syscall names on 32-bit")
Signed-off-by: Arnd Bergmann <>
Signed-off-by: Thomas Gleixner <>
Cc: Joseph Myers <>
Cc: Deepa Dinamani <>
Cc: Lukasz Majewski <>
Cc: Stepan Golosunov <>
Signed-off-by: Greg Kroah-Hartman <>

 arch/Kconfig |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


--- a/arch/Kconfig
+++ b/arch/Kconfig
@@ -764,7 +764,7 @@  config COMPAT_OLD_SIGACTION
 config 64BIT_TIME
-	def_bool ARCH_HAS_64BIT_TIME
+	def_bool y
 	  This should be selected by all architectures that need to support
 	  new system calls with a 64-bit time_t. This is relevant on all 32-bit