From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757904AbbJIKrQ (ORCPT ); Fri, 9 Oct 2015 06:47:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:40727 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757877AbbJIKrP (ORCPT ); Fri, 9 Oct 2015 06:47:15 -0400 Date: Fri, 9 Oct 2015 12:47:12 +0200 From: Miroslav Lichvar To: Thomas Gleixner Cc: Arnd Bergmann , linux-kernel@vger.kernel.org, y2038@lists.linaro.org, John Stultz , Prarit Bhargava , Richard Cochran Subject: Re: [PATCH] timekeeping: Limit system time to prevent 32-bit time_t overflow Message-ID: <20151009104712.GD2166@localhost> References: <1444224137-32510-1-git-send-email-mlichvar@redhat.com> <5753784.UXVo9jVTVp@wuerfel> <20151008062344.GO5778@localhost> <5836683.t4iPTifntz@wuerfel> <20151008093923.GQ5778@localhost> <20151009103421.GC2166@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 09, 2015 at 12:38:32PM +0200, Thomas Gleixner wrote: > On Fri, 9 Oct 2015, Miroslav Lichvar wrote: > > Do you feel the same about preventing the time from reaching > > KTIME_MAX? > > That's going to happen in ~500 years from now. At any time if you include accidents and attacks on services with the CAP_SYS_TIME capability (e.g. NTP/PTP implementations). Even with 32-bit time_t you are not safe, the time can be set forward by any amount with multiple adjtimex(ADJ_SETOFFSET) calls. -- Miroslav Lichvar