From: "Markus Rechberger" <markus.rechberger@amd.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] x86-64 ext2/ext3 datestamp problem
Date: Tue, 06 Feb 2007 22:57:46 +0100 [thread overview]
Message-ID: <45C8F9DA.6040906@amd.com> (raw)
In-Reply-To: <45C8F7E6.6060009@zytor.com>
H. Peter Anvin wrote:
> Markus Rechberger wrote:
>> Hi,
>>
>> there is an issue with ext2/ext3 date stamps, if someone creates a file
>> with a timestamp between 1902 and 1970(epoch 0) it will overflow and
>> result in a higher date than 2038.
>>
>> $ touch --date "1905-01-01" test
>> $ ls -lah test
>> -rw-r--r-- 1 root root 0 Jan 1 1905 test (this is a cached value here)
>> (remount the partition/clear the cache)
>> $ ls -lah test
>> -rw-r--r-- 1 root root 0 Feb 6 2041 test
>>
>> 10000101101111001100011001110000 .. -2051226000 (1905)
>> 10000101101111001100011001110000 .. 2243741296 (2041)
>>
>> this was tested against linus git tree
>>
>
> I believe the timestamp fields in ext2/ext3 are defined as unsigned.
>
> -hpa
>
>
My debian system's coreutils package only allows dates between 1902 and
2038, but it might be interesting to get that right if it's wrong.
touch (GNU coreutils) 5.97 just says invalid dateformat to 2050-01-01
Markus
--
Markus Rechberger
Operating System Research Center
AMD Saxony LLC & Co. KG
next prev parent reply other threads:[~2007-02-06 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 21:33 [patch] x86-64 ext2/ext3 datestamp problem Markus Rechberger
2007-02-06 21:40 ` Markus Rechberger
2007-02-06 21:49 ` H. Peter Anvin
2007-02-06 21:57 ` Markus Rechberger [this message]
2007-02-06 22:00 ` H. Peter Anvin
2007-02-06 22:07 ` Markus Rechberger
2007-02-06 22:06 ` H. Peter Anvin
2007-02-06 22:23 ` Markus Rechberger
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=45C8F9DA.6040906@amd.com \
--to=markus.rechberger@amd.com \
--cc=hpa@zytor.com \
--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