All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Fujita <a-fujita@rs.jp.nec.com>
To: Theodore Tso <tytso@mit.edu>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: [BUG] ext4 timestamps corruption
Date: Fri, 10 Jun 2011 17:27:40 +0900	[thread overview]
Message-ID: <4DF1D57C.3030107@rs.jp.nec.com> (raw)

Hi,

Officially, ext4 can handle its timestamps until 2514
with 32bit entries plus EPOCH_BIT (2bits).
But when timestamps values use 32+ bit
(e.g. 2038-01-19 9:14:08 0x0000000080000000),
we can get corrupted values.
Because sign bit is overwritten by transferring value
between kernel space and user space.

This can be happened with kernel 3.0.0-rc2 (Also older kernel)
on x86_64.

# This issue is already on Bugzilla,
  does anybody know this current status?
https://bugzilla.kernel.org/show_bug.cgi?id=23732

Reproduce steps are as follows:
# System time is set to UTC.

# mount -t ext4 /dev/sda8 /mnt/mp1

# touch -t 203801190314.08 /mnt/mp1/FILE

# umount /mnt/mp1
# mount -t ext4 /dev/sda8 /mnt/mp1

# stat /mnt/mp1/FILE
  File: `/mnt/mp1/FILE'
  Size: 0         	Blocks: 0          IO Block: 4096   regular empty file
Device: 808h/2056d	Inode: 12          Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 1901-12-13 20:45:52.000000000 +0000       <-----
Modify: 1901-12-13 20:45:52.000000000 +0000       <-----
Change: 2011-06-10 03:57:39.595385951 +0100
 Birth: -

Regards,
Akira Fujita


             reply	other threads:[~2011-06-10  8:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-10  8:27 Akira Fujita [this message]
2011-06-11 16:48 ` [BUG] ext4 timestamps corruption Andreas Dilger
2011-06-23  7:52   ` Akira Fujita
2011-06-23 22:37     ` Mark Harris
2011-06-24 22:46       ` Andreas Dilger
2011-06-25  5:12         ` Mark Harris
2011-06-27  9:04           ` Andreas Dilger
2011-07-05 10:51             ` Akira Fujita
2011-07-08 17:06               ` Mark Harris
2011-06-24 15:04     ` Andreas Dilger

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=4DF1D57C.3030107@rs.jp.nec.com \
    --to=a-fujita@rs.jp.nec.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.