From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
rtc-linux@googlegroups.com,
Alessandro Zummo <a.zummo@towertech.it>, Willy Tarreau <w@1wt.eu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtc: Add an option to invalidate dates in 2038
Date: Sun, 21 Feb 2016 12:40:20 +0000 [thread overview]
Message-ID: <20160221124020.49f39207@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20160220231702.GK2222@piout.net>
> It doesn't change anything for 64-bit systems, I've excluded them by
> using "depends on !64BIT". Right now, it doesn't change anything for
> 32-bit systems because either way, they will fail in 2038.
Which realistically won't actually matter because in 22 years time nobody
will be able to find a 32bit system in common use. If you look at x86
platforms today a Pentium Pro is already a collectors item. All of todays
locked down half-maintained embedded and phone devices will be at best
the digital equivalent of toxic waste if connected to anything.
> Won't we have to recompile every application to support 64-bit time on
> 32-bit system anyway? That will be a good time to remove that option.
How will you know when everyone has ? There's no "autodetect which
distribution I am running" feature.
> If the distribution don't recompile to support a 64-bit time, then the
> 32-bit systems will break in 2038 anyway and they will absolutely
> require my patch or something along those lines to still boot using
> systemd.
I disagree. Systemd has a serious robustness bug. Patch systemd to handle
timerd going off early and to take appropriate recovery action.
If you fix the systemd bug you'll also deal with a load of other weird
cornercases like 32bit guests on a 64bit host that accidentally ended up
post 2038, and every other freaky rtc failure.
Alan
next prev parent reply other threads:[~2016-02-21 17:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 19:10 Alexandre Belloni
2016-02-20 19:43 ` One Thousand Gnomes
2016-02-20 20:47 ` Alexandre Belloni
2016-02-20 22:16 ` Arnd Bergmann
2016-02-20 23:17 ` Alexandre Belloni
2016-02-20 23:42 ` Alexandre Belloni
2016-02-21 12:40 ` One Thousand Gnomes [this message]
2016-02-22 13:00 ` Alexandre Belloni
2016-02-22 13:43 ` One Thousand Gnomes
2016-02-22 15:44 ` Arnd Bergmann
2016-02-22 15:56 ` Alexandre Belloni
2016-02-22 16:18 ` Arnd Bergmann
2016-02-22 16:40 ` Alexandre Belloni
2016-02-22 16:41 ` Austin S. Hemmelgarn
2016-02-22 16:58 ` Alexandre Belloni
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=20160221124020.49f39207@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®