The POSIX standard requires that the ctime and mtime fields for memory-mapped files should be updated after a write reference to the memory region where the file data is mapped. At least FreeBSD 6.2 and HP-UX 11i implement this properly. Linux does not, which leads to data loss problems in database backup applications.
Kernel Bug Tracker contains more information about the problem: http://bugzilla.kernel.org/show_bug.cgi?id=2645 There have been several attempts in the past to address this issue. Following are a few links to LKML discussions related to this bug: http://lkml.org/lkml/2006/5/17/138 http://lkml.org/lkml/2007/2/21/242 http://lkml.org/lkml/2008/1/7/234 All earlier solutions were criticized. Some solutions did not handle memory-mapped block devices properly. Some led to forcing applications to explicitly call msync() to update file metadata. Some contained errors in using kernel synchronization primitives. In the two patches that follow, I would like to propose a new solution. This is the third version of my changes. This version takes into account all feedback I received for the two previous versions. The overall design remains basically the same as the one that was acked by Rick van Riel: http://lkml.org/lkml/2008/1/11/208 To the best of my knowledge, these patches are free of all the drawbacks found during previous attempts by Peter Staubach, Miklos Szeredi and myself. New since the previous version: 1) no need to explicitly call msync() to update file times; 2) changing block device data is visible to all device files associated with the block device; 3) in the cleanup part, the error checks are separated out as suggested by Rik van Riel; 4) some small refinements accodring to the LKML comments. This is how I tested the patches. 1. To test the features mentioned above, I wrote a unit test available from http://bugzilla.kernel.org/attachment.cgi?id=14430 I verified that the unit test passed successfully for both regular files and block device files. For the unit test I used the following architectures: 32-bit x86, x86_64 and MIPS32 (cross-compiled from x86_64). 2. I did build tests with allmodconfig and allyesconfig on x86_64. 3. I ran the following test cases from the LTP test suite: msync01 msync02 msync03 msync04 msync05 mmapstress01 mmapstress09 mmapstress10 No regressions were found by these test cases. I think that the bug #2645 is resolved by these patches. Please apply. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
