From: Miroslav Lichvar <mlichvar@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, y2038@lists.linaro.org,
John Stultz <john.stultz@linaro.org>,
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: Fri, 9 Oct 2015 12:34:21 +0200 [thread overview]
Message-ID: <20151009103421.GC2166@localhost> (raw)
In-Reply-To: <alpine.DEB.2.11.1510091032100.6097@nanos>
On Fri, Oct 09, 2015 at 10:46:16AM +0100, Thomas Gleixner wrote:
> On Thu, 8 Oct 2015, Miroslav Lichvar wrote:
> > 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 :).
>
> As Arnd said, you are creating a wrong sense of safety. They fall off
> the cliff with your changes as well. The fall is just different. Think
> about timeouts, user space overflows of time_t etc.
I think vast majority of them won't fall. It doesn't prevent all
problems, but at least the userspace agrees with kernel on what the
current time it is, that looks to me like the most difficult one to
fix in applications.
> We need to fix all of it, no matter what.
Yeah, that would be nice, but I don't think it's realistic.
Do you feel the same about preventing the time from reaching
KTIME_MAX?
--
Miroslav Lichvar
next prev parent reply other threads:[~2015-10-09 10:34 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
2015-10-09 9:46 ` Thomas Gleixner
2015-10-09 10:34 ` Miroslav Lichvar [this message]
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=20151009103421.GC2166@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox