* [PATCH 0/2][RFC][BUG] msync: another attempt to fix the ctime/mtime issue
@ 2008-01-11 0:38 ` Anton Salikhmetov, Anton Salikhmetov
0 siblings, 0 replies; 2+ messages in thread
From: Anton Salikhmetov @ 2008-01-11 0:38 UTC (permalink / raw)
To: linux-mm
Cc: jakob, linux-kernel, Valdis.Kletnieks, riel, ksm, staubach,
jesper.juhl
From: Anton Salikhmetov <salikhmetov@gmail.com>
I would like to propose my second solution for the bug #2645 from the
kernel bug tracker:
http://bugzilla.kernel.org/show_bug.cgi?id=2645
You may find the relevant background information as well as an extensive
discussion of my previous solution using the following link:
http://lkml.org/lkml/2008/1/9/387
The short change list:
1) taking into account the intervening sync() call which Peter Staubach
has mentioned (http://lkml.org/lkml/2008/1/9/267);
2) splitting the solution into two patches: code cleanup and functional
changes;
3) updating ctime and mtime in do_fsync(), due to that the file time stamps
get updated even without any explicit call to msync().
Please note that the second patch (functional changes) should be applied
on top of the first one (code cleanup).
Also I changed my unit test due to Peter's remark:
http://lkml.org/lkml/2008/1/9/267
The new version of the unit test can be found here:
http://bugzilla.kernel.org/attachment.cgi?id=14398&action=view
No regression was found when I ran the test cases for the msync() system
call from the LTP test suite (msync01 - msync05, mmapstress01,
mmapstress09, and mmapstress10).
^ permalink raw reply [flat|nested] 2+ messages in thread
* [PATCH 0/2][RFC][BUG] msync: another attempt to fix the ctime/mtime issue
@ 2008-01-11 0:38 ` Anton Salikhmetov, Anton Salikhmetov
0 siblings, 0 replies; 2+ messages in thread
From: Anton Salikhmetov, Anton Salikhmetov @ 2008-01-11 0:38 UTC (permalink / raw)
To: linux-mm
Cc: jakob, linux-kernel, Valdis.Kletnieks, riel, ksm, staubach,
jesper.juhl
I would like to propose my second solution for the bug #2645 from the
kernel bug tracker:
http://bugzilla.kernel.org/show_bug.cgi?id=2645
You may find the relevant background information as well as an extensive
discussion of my previous solution using the following link:
http://lkml.org/lkml/2008/1/9/387
The short change list:
1) taking into account the intervening sync() call which Peter Staubach
has mentioned (http://lkml.org/lkml/2008/1/9/267);
2) splitting the solution into two patches: code cleanup and functional
changes;
3) updating ctime and mtime in do_fsync(), due to that the file time stamps
get updated even without any explicit call to msync().
Please note that the second patch (functional changes) should be applied
on top of the first one (code cleanup).
Also I changed my unit test due to Peter's remark:
http://lkml.org/lkml/2008/1/9/267
The new version of the unit test can be found here:
http://bugzilla.kernel.org/attachment.cgi?id=14398&action=view
No regression was found when I ran the test cases for the msync() system
call from the LTP test suite (msync01 - msync05, mmapstress01,
mmapstress09, and mmapstress10).
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-01-11 0:38 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-01-11 0:38 [PATCH 0/2][RFC][BUG] msync: another attempt to fix the ctime/mtime issue Anton Salikhmetov
2008-01-11 0:38 ` Anton Salikhmetov, Anton Salikhmetov
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.