Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756533AbbDOVcW (ORCPT ); Wed, 15 Apr 2015 17:32:22 -0400 Received: from 251.110.2.81.in-addr.arpa ([81.2.110.251]:43771 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754806AbbDOVcP (ORCPT ); Wed, 15 Apr 2015 17:32:15 -0400 Date: Wed, 15 Apr 2015 22:31:54 +0100 From: One Thousand Gnomes To: Miroslav Lichvar Cc: linux-kernel@vger.kernel.org, John Stultz , Thomas Gleixner , Prarit Bhargava , Richard Cochran , Arnd Bergmann Subject: Re: [RFC][PATCH] timekeeping: Limit system time to prevent 32-bit time_t overflow Message-ID: <20150415223154.65c8d05e@lxorguk.ukuu.org.uk> In-Reply-To: <1429112488-12574-1-git-send-email-mlichvar@redhat.com> References: <1429112488-12574-1-git-send-email-mlichvar@redhat.com> Organization: Intel Corporation X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 763 Lines: 20 On Wed, 15 Apr 2015 17:41:28 +0200 Miroslav Lichvar wrote: > On systems with 32-bit time_t, it seems there are quite a few problems > that applications may have with time overflowing in year 2038. Beside Even ext4 is still broken for 2038. > larger value. When the maximum is reached in normal time accumulation, > the clock will be stepped back by one week. Which itself is open to exploits and dirty tricks and causes bizarre problems. IMHO it doesn't actually improve the situation. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/