From: Andrew Morton <akpm@linux-foundation.org>
To: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Fw: [Bugme-new] [Bug 8643] New: Bug with negative timestamps on 64bit machines
Date: Sat, 16 Jun 2007 23:05:27 -0700 [thread overview]
Message-ID: <20070616230527.e26f66d9.akpm@linux-foundation.org> (raw)
someone ort to fix this
Begin forwarded message:
Date: Sat, 16 Jun 2007 17:50:35 -0700 (PDT)
From: bugme-daemon@bugzilla.kernel.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 8643] New: Bug with negative timestamps on 64bit machines
http://bugzilla.kernel.org/show_bug.cgi?id=8643
Summary: Bug with negative timestamps on 64bit machines
Product: File System
Version: 2.5
KernelVersion: 2.6.21-1.3228.fc7
Platform: All
OS/Version: Linux
Tree: Fedora
Status: NEW
Severity: normal
Priority: P1
Component: ext3
AssignedTo: akpm@osdl.org
ReportedBy: markus.mottl@gmail.com
Most recent kernel where this bug did not occur:
Distribution: Fedora Core 7
Hardware Environment: AMD Athlon 64
Software Environment:
Problem Description:
Negative timestamps (i.e. before 1970) are incorrectly handled due to some
obvious 64bit issues. They show up normally as long as the cache has not been
purged.
Steps to reproduce:
Touch a file in an ext3-file system with a negative timestamp, e.g.:
# touch -t 196901010000 /opt/foo
Unless you have been writing a lot of data to this partition after the last
command, the next one should display the following:
# ls -l /opt/foo
-rw-r--r-- 1 root root 0 1969-01-01 00:00 /opt/foo
This is still correct. But now we purge the file system cache by unmounting
and mounting the partition again:
# umount /opt/foo
# mount /opt/foo
Now the timestamp will be corrupted:
# ls -l /opt/foo
-rw-r--r-- 1 root root 0 2105-02-07 06:28 /opt/foo
It seems obvious that the upper 32 bits of the 64 bits representing the time
stamp get lost, which explains the above observation.
On 32bit architectures there is no such problem. I haven't managed to
reproduce this problem with other file systems (e.g. XFS).
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2007-06-17 6:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 6:05 Andrew Morton [this message]
2007-06-17 9:43 ` Fw: [Bugme-new] [Bug 8643] New: Bug with negative timestamps on 64bit machines Dmitriy Monakhov
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=20070616230527.e26f66d9.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-ext4@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 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.