Subject: Re: Timestamp of file modified through mmap are not changed in 2.6
From: Alexander Nyberg <alexn@dsv.su.se>
To: Xavier Roche <roche+kml2@exalead.com>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <4256A06C.8020304@exalead.com>
References: <4256A06C.8020304@exalead.com>
Content-Type: text/plain
Date: Fri, 08 Apr 2005 17:46:28 +0200
Message-Id: <1112975188.16451.14.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1148
Lines: 26

> Timestamp of file modified through mmap are not changed in 2.6 (even 
> after msync()). Observations on 2.4 and 2.6 kernels:
> - on 2.4, timestamps are altered a few seconds after the program exits.
> - on 2.6, timestamps are never altered.
> 
> Is this behaviour a normal behaviour ?
> 
> Program example to reproduce the bug (you need to create a "test" file 
> in the current directory first):

Yeah there's been at least one bug on bugzilla open for this, and I
recall the posix specification saying the times on files shall be
updated on mmap file changes (which makes sense too).

Doing it at msync is easy, keeping track of memory mapped data etc. is
more cumbersome. I sent a patch doing this a while ago (doesn't work now
due to msync rework, think it was the 4-level changes) that worked well
for me but nobody seemed to be be overwhelmed by it :-)

http://lkml.org/lkml/diff/2004/12/5/95/1

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/