[lkml]   [2017]   [Nov]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
Subject[PATCH 5/9] y2038: introduce CONFIG_64BIT_TIME
From: Arnd Bergmann <>

There are a total of 53 system calls (aside from ioctl) that pass a time_t
or derived data structure as an argument, and in order to extend time_t
to 64-bit, we have to replace them with new system calls and keep providing
backwards compatibility.

To avoid adding completely new and untested code for this purpose, we
introduce a new CONFIG_64BIT_TIME symbol. Every architecture that supports
new 64 bit time_t syscalls enables this config via ARCH_HAS_64BIT_TIME.

After this is done for all architectures, the CONFIG_64BIT_TIME symbol
can be made a user-selected option, to enable users to build a kernel
that only provides y2038-safe system calls by making 32 time_t syscalls
conditionally included based on the above config.

Signed-off-by: Arnd Bergmann <>
Signed-off-by: Deepa Dinamani <>
arch/Kconfig | 11 +++++++++++
1 file changed, 11 insertions(+)

diff --git a/arch/Kconfig b/arch/Kconfig
index 8911ff37335a..3266ac1a4ff7 100644
--- a/arch/Kconfig
+++ b/arch/Kconfig
@@ -875,6 +875,17 @@ config OLD_SIGACTION

+ def_bool n
+ def_bool ARCH_HAS_64BIT_TIME
+ help
+ 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
+ architectures, and 64-bit architectures as part of compat syscall
+ handling.

 \ /
  Last update: 2017-11-10 23:45    [W:0.121 / U:0.024 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site