From: Miroslav Lichvar <mlichvar@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org, y2038@lists.linaro.org,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Prarit Bhargava <prarit@redhat.com>,
Richard Cochran <richardcochran@gmail.com>
Subject: Re: [PATCH] timekeeping: Limit system time to prevent 32-bit time_t overflow
Date: Thu, 8 Oct 2015 11:39:23 +0200 [thread overview]
Message-ID: <20151008093923.GQ5778@localhost> (raw)
In-Reply-To: <5836683.t4iPTifntz@wuerfel>
On Thu, Oct 08, 2015 at 10:52:05AM +0200, Arnd Bergmann wrote:
> On Thursday 08 October 2015 08:23:44 Miroslav Lichvar wrote:
> > The difference is that with the one-week step the kernel and userspace
> > still agree on the current time and it is always valid from the kernel
> > point of view, absolute timers can be set, etc.
>
> Ok, I can see that as an improvement, but it still seems to give
> a false sense of safety, and I feel we really should not have any code
> rely on this behavior.
Applications are not allowed to rely on system time being sane?
To me the current behavior looks like the kernel is throwing the
applications off a cliff, while it's the only thing that can fly :).
--
Miroslav Lichvar
next prev parent reply other threads:[~2015-10-08 9:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 13:22 [PATCH] timekeeping: Limit system time to prevent 32-bit time_t overflow Miroslav Lichvar
2015-10-07 13:47 ` Arnd Bergmann
2015-10-07 14:23 ` Miroslav Lichvar
2015-10-07 15:10 ` Arnd Bergmann
2015-10-08 6:23 ` Miroslav Lichvar
2015-10-08 8:52 ` Arnd Bergmann
2015-10-08 9:39 ` Miroslav Lichvar [this message]
2015-10-09 9:46 ` Thomas Gleixner
2015-10-09 10:34 ` Miroslav Lichvar
2015-10-09 10:38 ` Thomas Gleixner
2015-10-09 10:47 ` Miroslav Lichvar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151008093923.GQ5778@localhost \
--to=mlichvar@redhat.com \
--cc=arnd@arndb.de \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.de \
--cc=y2038@lists.linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.