public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Petr Titěra" <petr@titera.eu>
To: linux-kernel@vger.kernel.org
Subject: Wrong atime on recent kernels
Date: Mon, 14 Dec 2009 22:17:50 +0100	[thread overview]
Message-ID: <4B26AB7E.9020208@titera.eu> (raw)

Hello,

       I see some strange file modification times recently. It seems to 
me that in some situations, kernel allows to set nanoseconds part of  
file access, modification or change time  to 100000000 ns. Problem seems 
to be in some generic part of kernel because I see it on several 
different filesysytems (ext4 and nilf2). These is I've got during my 
testing on kernel  2.6.32-tip-08309-gad8e75a.

  File: `./Documentation/dvb/contributors.txt'
  Size: 3035            Blocks: 8          IO Block: 4096   regular file
Device: fe04h/65028d    Inode: 818         Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2009-12-14 10:29:04.1000000000 +0100
Modify: 2009-12-14 10:29:04.1000000000 +0100
Change: 2009-12-14 10:29:04.1000000000 +0100

See that all times of that file ends with 1e6 nanoseconds.

Petr Titera

             reply	other threads:[~2009-12-14 21:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 21:17 Petr Titěra [this message]
2009-12-14 21:41 ` Wrong atime on recent kernels Andi Kleen
2009-12-14 21:59   ` Petr Titěra
2009-12-14 21:45 ` john stultz
     [not found]   ` <4B29494B.4010305@titera.eu>
2009-12-17  1:21     ` john stultz
2009-12-17  3:26     ` john stultz
2009-12-17 11:04       ` Petr Titěra
2009-12-17 21:19         ` john stultz
2009-12-18  3:13         ` john stultz
2009-12-20 22:29           ` Petr Titěra
2009-12-20 23:31             ` Petr Titěra
2009-12-21 21:16               ` john stultz
2009-12-22 15:50                 ` Petr Titěra

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=4B26AB7E.9020208@titera.eu \
    --to=petr@titera.eu \
    --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