From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752869AbbCKDUX (ORCPT ); Tue, 10 Mar 2015 23:20:23 -0400 Received: from m15-112.126.com ([220.181.15.112]:48927 "EHLO m15-112.126.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752207AbbCKDTZ (ORCPT ); Tue, 10 Mar 2015 23:19:25 -0400 From: Xunlei Pang To: linux-kernel@vger.kernel.org Cc: rtc-linux@googlegroups.com, Thomas Gleixner , Alessandro Zummo , John Stultz , Arnd Bergmann , linux-omap@vger.kernel.org, Tony Lindgren , linux-tegra@vger.kernel.org, Stephen Warren , linux390@de.ibm.com, Martin Schwidefsky , Ralf Baechle , Arnd Bergmann , Xunlei Pang Subject: [PATCH 0/8] Add y2038 safe replacements for read_boot_clock(), read_persistent_clock() and update_persistent_clock() Date: Wed, 11 Mar 2015 11:15:07 +0800 Message-Id: <1426043715-22043-1-git-send-email-xlpang@126.com> X-Mailer: git-send-email 1.9.1 X-CM-TRANSID: DMmowEAp51Z4s_9UJTpwAw--.1055S2 X-Coremail-Antispam: 1Uf129KBjvJXoWxZw1rGr15XrWrGw48AF1kZrb_yoW5Gw4kp3 ySyr9xWr4kJ345urnxtwnrZr1akw1rKF43t34fJ34fAr1jvF1xXFy8CayFvrZxJFyfAwsF vFWUZ3WDWr1DZrUanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDUYxBIdaVFxhVjvjDU0xZFpf9x07jzmhrUUUUU= X-Originating-IP: [210.21.223.3] X-CM-SenderInfo: p0ost0bj6rjloofrz/1tbiWwu5v1PM7Z6ENwAAsJ Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Xunlei Pang read_boot_clock(), read_persistent_clock() and update_persistent_clock() all use timespec which may have "y2038 problem", thus we are planning on converting all of them to use timespec64. The approach we're using is: 1) First of all, add the "__weak" implementaion of xxx_clock64() which uses xxx_clock() and timespec64. Let's take read_persistent_clock() as an example. We can create its y2038-safe version below: void __weak read_persistent_clock64(struct timespec64 *ts64) { struct timespec ts; read_persistent_clock(&ts); *ts64 = timespec_to_timespec64(ts); } Then, replace all the call sites of xxx_clock() with xxx_clock64() except the one used by xxx_clock64(). 2) Convert every architecture specific xxx_clock() to xxx_clock64() one by one. At this point, we can convert the three functions at a time if needed, because most time they're correlated. 3) Remove xxx_clock() after all its architecture specific implementations have been converted to use corresponding y2038 safe xxx_clock64(). This patchset firstly finished the step1 for all the three functions, then focused on read_boot_clock() which is simple to go on with step2 and step3 as a whole show. As for read_persistent_clock() and update_persistent_clock() which are more complex, requiring many efforts to convert every architecture specific implementation gradually. The approach used here is Suggested-by: "Arnd Bergmann " Xunlei Pang (8): time: Add y2038 safe read_boot_clock64() time: Add y2038 safe read_persistent_clock64() time: Add y2038 safe update_persistent_clock64() ARM: OMAP: 32k counter: Provide y2038-safe omap_read_persistent_clock() replacement ARM: tegra: clock: Provide y2038-safe tegra_read_persistent_clock() replacement ARM: time: Provide read_boot_clock64() and read_persistent_clock64() s390: time: Provide read_boot_clock64() and read_persistent_clock64() time: Remove read_boot_clock() arch/arm/include/asm/mach/time.h | 3 +-- arch/arm/kernel/time.c | 6 +++--- arch/arm/plat-omap/counter_32k.c | 18 ++++++------------ arch/mips/lasat/sysctl.c | 4 ++-- arch/s390/include/asm/timex.h | 4 ++-- arch/s390/kernel/debug.c | 4 ++-- arch/s390/kernel/time.c | 6 +++--- drivers/clocksource/tegra20_timer.c | 15 +++++++-------- drivers/rtc/systohc.c | 2 +- include/linux/timekeeping.h | 4 +++- kernel/time/ntp.c | 13 ++++++++++++- kernel/time/timekeeping.c | 31 ++++++++++++++++--------------- 12 files changed, 58 insertions(+), 52 deletions(-) -- 1.9.1