All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: John Stultz <john.stultz@linaro.org>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Dealing with 2038
Date: Fri, 09 May 2014 10:30:42 -0700	[thread overview]
Message-ID: <536D10C2.5070907@zytor.com> (raw)
In-Reply-To: <20140506022158.GA1499@thin>

On 05/05/2014 07:21 PM, Josh Triplett wrote:
> 
> 64-bit off_t support seems like a similar issue; all the kernel
> interfaces support 64-bit off_t, and glibc has #defines for
> 64-bit off_t, but a large number of userspace programs don't bother to
> define them.
> 
> That seems like the right path to transition time_t as well.
> 

The transition to a 64-bit off_t was still enormously complex, which
involved defining entirely new types and APIs which were then optionally
#defined to the traditional names.  Hence the _FILE_OFFSET_BITS opt-in.

For time_t it is even worse.

	-hpa

  parent reply	other threads:[~2014-05-09 17:30 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 18:33 [Ksummit-discuss] [CORE TOPIC] Dealing with 2038 John Stultz
2014-05-05 19:23 ` Andy Lutomirski
2014-05-05 20:53 ` josh
2014-05-05 23:20   ` Andy Lutomirski
2014-05-06  2:12   ` H. Peter Anvin
2014-05-06  2:21     ` Josh Triplett
2014-05-06 12:57       ` Theodore Ts'o
2014-05-06 17:53         ` John Stultz
2014-05-06 18:20           ` Arnd Bergmann
2014-05-06 20:19             ` Theodore Ts'o
2014-05-06 20:33               ` josh
2014-05-06 20:50                 ` Theodore Ts'o
2014-05-06 22:06                   ` John Stultz
2014-05-07  2:07                     ` Theodore Ts'o
2014-05-07 11:19                       ` Jonathan Corbet
2014-05-07 17:28                       ` John Stultz
2014-05-09 15:05                         ` Theodore Ts'o
2014-05-08 20:37                       ` Ben Hutchings
2014-05-09 15:10                         ` Theodore Ts'o
2014-05-09 20:39                           ` Arnd Bergmann
2014-05-09 22:33                             ` Josh Triplett
2014-05-10  0:16                               ` H. Peter Anvin
2014-05-10  1:44                                 ` Rafael J. Wysocki
2014-05-15 12:18                                 ` Grant Likely
2014-05-15 17:20                                   ` H. Peter Anvin
2014-05-16  2:50                                     ` Jason Cooper
2014-05-10  0:19                               ` Andy Lutomirski
2014-05-06 21:17               ` Daniel Phillips
2014-05-06 21:56                 ` Luck, Tony
2014-05-07  1:56                   ` Daniel Phillips
2014-05-07 14:00         ` Grant Likely
2014-05-09 17:30       ` H. Peter Anvin [this message]
2014-05-06  1:25 ` Li Zefan

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=536D10C2.5070907@zytor.com \
    --to=hpa@zytor.com \
    --cc=john.stultz@linaro.org \
    --cc=josh@joshtriplett.org \
    --cc=ksummit-discuss@lists.linuxfoundation.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.