public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Petr Titěra" <petr@titera.eu>
To: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: Wrong atime on recent kernels
Date: Mon, 14 Dec 2009 22:59:55 +0100	[thread overview]
Message-ID: <4B26B55B.8010302@titera.eu> (raw)
In-Reply-To: <87d42hxmgd.fsf@basil.nowhere.org>

Andi Kleen napsal(a):
> Petr Titěra <petr@titera.eu> writes:
>
>   
>> 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.
>>     
>
> Do you know which kernel was the last one to be not showing this?
>
>   
To Be honest I'm not sure. I remember that I've seen it for the first
time when I tried to install kernel-2.6.32-0.65.rc8.git5.fc13.i686
package from Fedora Rawhide and that was on 7th December. The only
kernels I could be running at that time are:
2.6.32-rc8-tip-02151-gf00b740, 2.6.32-tip-02531-gbbbe9f2 or
2.6.32-tip-02695-g4dc2ffc.

> Is 2.6.32 plain ok?
>
>   
Will test.

> -Andi
>
>   

Petr


  reply	other threads:[~2009-12-14 22:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 21:17 Wrong atime on recent kernels Petr Titěra
2009-12-14 21:41 ` Andi Kleen
2009-12-14 21:59   ` Petr Titěra [this message]
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=4B26B55B.8010302@titera.eu \
    --to=petr@titera.eu \
    --cc=andi@firstfloor.org \
    --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