From: Anton Salikhmetov <salikhmetov@gmail.com>
From: Anton Salikhmetov <salikhmetov@gmail.com>
To: linux-mm@kvack.org
Cc: jakob@unthought.net, linux-kernel@vger.kernel.org,
Valdis.Kletnieks@vt.edu, riel@redhat.com, ksm@42.dk,
staubach@redhat.com, jesper.juhl@gmail.com
Subject: [PATCH 0/2][RFC][BUG] msync: another attempt to fix the ctime/mtime issue
Date: Fri, 11 Jan 2008 03:38:36 +0300 [thread overview]
Message-ID: <1200011916.19293.91.camel@codedot> (raw)
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>
reply other threads:[~2008-01-11 0:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1200011916.19293.91.camel@codedot \
--to=salikhmetov@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=jakob@unthought.net \
--cc=jesper.juhl@gmail.com \
--cc=ksm@42.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=staubach@redhat.com \
/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