linux-kernel - Re: [PATCH 00/19] converting system calls to 64-bit time

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: <1430983678.8171.23.camel@x220>
Date:	Thu, 07 May 2015 09:27:58 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	y2038@...ts.linaro.org, baolin.wang@...aro.org, tglx@...utronix.de,
	albert.aribaud@...ev.fr, john.stultz@...aro.org,
	bamvor.zhangjian@...aro.org, ruchandani.tina@...il.com,
	linux-api@...r.kernel.org, linux-kernel@...r.kernel.org,
	libc-alpha@...rceware.org
Subject: Re: [PATCH 00/19] converting system calls to 64-bit time_t, part 1

On Wed, 2015-05-06 at 18:30 +0200, Arnd Bergmann wrote:
> * After all system calls are converted, we can change one architecture
>   at a time to select ARCH_HAS_COMPAT_TIME, and modify its system
>   call table accordingly. In this version, I do it for ARM32, x86-32,
>   and x86-64 for demonstration purposes.

Perhaps this was correct for your first draft. Because this series adds
ARCH_HAS_COMPAT_TIME in 04/19, but it doesn't add any selects of that
symbol, does it? As far as I can see ARCH_HAS_COMPAT_TIME simply
functions as an alias for COMPAT in this series.

> * A follow-up series changes over all other architectures.
> 
> * The last patch in the series changes the CONFIG_COMPAT_TIME
>   Kconfig symbol to be user visible. Disabling this symbol will
>   get you a kernel that intentionally breaks support for old tasks
>   in order to provide an interface that will survive 2038.

This doesn't happen in 19/19, or in any other patch in this series.
Maybe also something that has changed since the first draft.

>   This is meant mostly as a debugging help for now, to let people
>   build a y2038 safe distro, but at some point in the 2030s, we
>   should remove that option and all the compat handling.

Thanks,


Paul Bolle

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/