From: Thorsten Kukuk <kukuk@suse.com>
To: libc-alpha@sourceware.org
Subject: 64-bit time_t and __WORDSIZE_TIME64_COMPAT32
Date: Wed, 8 Feb 2023 10:18:22 +0100 [thread overview]
Message-ID: <20230208091821.GA2282@suse.com> (raw)
Hi,
Currently on 64bit architectures like x86-64 we define
__WORDSIZE_TIME64_COMPAT32 as 1, which leads to a 32bit time_t in utmp,
wtmp, lastlog and similar files.
This leads to the problem, that utmp, wtmp and lastlog stops working
in 2038 even if you have a pure 64bit system.
Since I couldn't found anything about this, was it ever discussed or is
there any plan how to handle this?
Looking at my system there are much more systems using this interface
than I thought, so my first idea of just deprecating this interface is
no solution.
I think the only solution would be additional functions like for other
32bit time_t functions and use symbol versioning for it?
Thorsten
--
Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies
SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nuernberg, Germany
Managing Director: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)
next reply other threads:[~2023-02-08 9:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 9:18 Thorsten Kukuk [this message]
2023-02-08 10:06 ` Andreas Schwab
[not found] ` <0869a6f98f29405eb431f63db593c490@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-02-08 10:11 ` Thorsten Kukuk
2023-02-08 10:17 ` Andreas Schwab
[not found] ` <d2f1ee273add4af0868e07dc32542687@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-02-08 10:22 ` Thorsten Kukuk
2023-02-08 10:27 ` Andreas Schwab
[not found] ` <7485b79473614eaa994d3ea79c91629a@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-02-08 10:38 ` Thorsten Kukuk
2023-02-08 11:48 ` Adhemerval Zanella Netto
2023-02-14 8:24 ` Thorsten Kukuk
2023-02-14 8:59 ` Florian Weimer
[not found] ` <3230d2f8fa214c268cba52e699c14ae2@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-02-14 9:26 ` Thorsten Kukuk
2023-02-14 14:28 ` Adhemerval Zanella Netto
2023-02-16 13:59 ` Thorsten Kukuk
2023-04-11 11:40 ` Thorsten Kukuk
2023-04-11 13:23 ` Adhemerval Zanella Netto
2023-09-25 7:30 ` Thorsten Kukuk
2023-04-11 21:41 ` Paul Eggert
2023-04-12 6:55 ` Thorsten Kukuk
2023-04-12 23:36 ` Paul Eggert
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=20230208091821.GA2282@suse.com \
--to=kukuk@suse.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).