lkml.org 
[lkml]   [2002]   [Jun]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: 2.4.18 no timestamp update on modified mmapped files
Date
On Mon, 10 Jun 2002 23:49:02 -0700, 
Andrew Morton <akpm@zip.com.au> wrote:
>Keith Owens wrote:
>> On Mon, 10 Jun 2002 23:17:27 -0700,
>> Andrew Morton <akpm@zip.com.au> wrote:
>> > The st_ctime and st_mtime fields of a file that is mapped with MAP_SHARED
>> > and PROT_WRITE shall be marked for update at some point in the interval
>> > between a write reference to the mapped region and the next call to msync() with
>> > MS_ASYNC or MS_SYNC for that portion of the file by any process. If there is
>> > no such call and if the underlying file is modified as a result of a write reference,
>> > then these fields shall be marked for update at some time after the write reference.
>>
>> That says nothing about a file where the only updates are via mmap. My
>> file had grown to its final size so there were no more writes, only
>> pages being dirtied via mmap.
>
>It is specifically referring to updates via mmap! "a write reference
>to the mapped region". This is the mmap documentation.

I saw "write reference" and my brain translated that to "write()". I
blame the long weekend.

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:26    [W:0.068 / U:0.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site