linux-kernel - [PATCH 5/9] y2038: introduce CONFIG_64BIT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20171110224259.15930-6-deepa.kernel@gmail.com>
Date:   Fri, 10 Nov 2017 14:42:55 -0800
From:   Deepa Dinamani <deepa.kernel@...il.com>
To:     tglx@...utronix.de, john.stultz@...aro.org
Cc:     linux-kernel@...r.kernel.org, arnd@...db.de, y2038@...ts.linaro.org
Subject: [PATCH 5/9] y2038: introduce CONFIG_64BIT_TIME

From: Arnd Bergmann <arnd@...db.de>

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 <arnd@...db.de>
Signed-off-by: Deepa Dinamani <deepa.kernel@...il.com>
---
 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
 config COMPAT_OLD_SIGACTION
 	bool

+config ARCH_HAS_64BIT_TIME
+	def_bool n
+
+config CONFIG_64BIT_TIME
+	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.
+
 config ARCH_NO_COHERENT_DMA_MMAP
 	bool

-- 
2.11.0