From: Peter Staubach <staubach@redhat.com>
To: Marek Michalkiewicz <marekm@amelek.gda.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mmap / mtime updates
Date: Thu, 11 Jan 2007 17:46:52 -0500 [thread overview]
Message-ID: <45A6BE5C.9040904@redhat.com> (raw)
In-Reply-To: <20070109220940.GA16978@amelek.gda.pl>
Marek Michalkiewicz wrote:
> Hello,
>
> What is the current status of the bug where modifications to file
> contents made via mmap fail to update mtime of the file?
>
> This was discussed a few months ago in this thread:
>
> http://lkml.org/lkml/2006/5/17/138
>
> where patches have been posted, but it seems that no final solution
> has been agreed on and applied to the kernel tree. Updating ctime
> and mtime appears to be required by the standard:
>
> http://www.opengroup.org/onlinepubs/009695399/functions/mmap.html
>
> 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.
>
> and failing to do it can lead to potential data loss as well, if
> modified files are not backed up (I'm seeing the problem with Samba
> tdb files not being backed up by rsnapshot, for example).
I am working on porting the patches to the current upstream kernel.
As soon as I complete this work, then I will repost the patch and
we'll see where things go then.
Thanx...
ps
prev parent reply other threads:[~2007-01-11 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 22:09 mmap / mtime updates Marek Michalkiewicz
2007-01-11 22:46 ` Peter Staubach [this message]
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=45A6BE5C.9040904@redhat.com \
--to=staubach@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marekm@amelek.gda.pl \
/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 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.