From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: year 2038 problem on x86-64
Date: Wed, 22 Sep 2004 23:45:29 +0200 [thread overview]
Message-ID: <20040922214529.GA803@elf.ucw.cz> (raw)
In-Reply-To: <20040922213028.GE14891@elf.ucw.cz>
Hi!
> For testing (read() and write() is returning wrong value on 2.4
> kernels) I played a bit with really big numbers... And I found out we
> have year 9223372034708485227 problem ;-).
And we have some nearer problems, too.
#ifdef __ARCH_WANT_SYS_TIME
/*
* sys_time() can be implemented in user-level using
* sys_gettimeofday(). Is this for backwards compatibility? If so,
* why not move it into the appropriate arch directory (for those
* architectures that need it).
*
* XXX This function is NOT 64-bit clean!
*/
asmlinkage long sys_time(int __user * tloc)
{
int i;
struct timeval tv;
do_gettimeofday(&tv);
i = tv.tv_sec;
if (tloc) {
if (put_user(i,tloc))
i = -EFAULT;
}
return i;
}
... __ARCH_WANT_SYS_TIME actually is set on x86-64.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2004-09-22 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 21:30 year 9223372034708485227 problem Pavel Machek
2004-09-22 21:45 ` Pavel Machek [this message]
[not found] <2Hn0k-2wz-9@gated-at.bofh.it>
[not found] ` <2HnjK-2Ha-3@gated-at.bofh.it>
2004-09-22 22:27 ` year 2038 problem on x86-64 Andi Kleen
2004-09-22 22:34 ` Pavel Machek
[not found] <2HnMR-35F-55@gated-at.bofh.it>
[not found] ` <2HnMR-35F-57@gated-at.bofh.it>
[not found] ` <2HnMR-35F-53@gated-at.bofh.it>
[not found] ` <2HnWp-3b7-25@gated-at.bofh.it>
2004-09-22 22:51 ` Andi Kleen
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=20040922214529.GA803@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.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