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  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]
Date:   Thu, 14 Dec 2017 23:22:34 +0000
From:   Ben Hutchings <ben.hutchings@...ethink.co.uk>
To:     Deepa Dinamani <deepa.kernel@...il.com>, tglx@...utronix.de,
        john.stultz@...aro.org
Cc:     y2038@...ts.linaro.org, linux-kernel@...r.kernel.org, arnd@...db.de
Subject: Re: [Y2038] [PATCH v2 04/10] arch: introduce CONFIG_64BIT_TIME

On Mon, 2017-11-27 at 11:30 -0800, Deepa Dinamani wrote:
> 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
> will be deleted.
> 
> 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 4f03534bfa6b..11810c29c1fa 100644
> --- a/arch/Kconfig
> +++ b/arch/Kconfig
> @@ -873,6 +873,17 @@ config OLD_SIGACTION
>  config COMPAT_OLD_SIGACTION
> >  	bool
>  
> +config ARCH_HAS_64BIT_TIME
> +	def_bool n
> +
> +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.

Doesn't this text belong with ARCH_HAS_64BIT_TIME?

Ben.

> +
>  config ARCH_NO_COHERENT_DMA_MMAP
>  	bool
>  
-- 
Ben Hutchings
Software Developer, Codethink Ltd.

Powered by blists - more mailing lists