linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: staubach@redhat.com
Cc: miklos@szeredi.hu, akpm@linux-foundation.org, hugh@veritas.com,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] update ctime and mtime for mmaped write
Date: Thu, 22 Feb 2007 21:48:11 +0100	[thread overview]
Message-ID: <E1HKKrL-0006k6-00@dorka.pomaz.szeredi.hu> (raw)
In-Reply-To: <45DDF9C1.4090003@redhat.com> (message from Peter Staubach on Thu, 22 Feb 2007 15:14:57 -0500)

> > __fput() will be called when there are no more references to 'file',
> > then it will update the time if the flag is set.  This applies to
> > regular files as well as devices.
> >
> >   
> 
> I suspect that you will find that, for a block device, the wrong inode
> gets updated.  That's where the bd_inode_update_time() portion of my
> proposed patch came from.

How horrible :( I haven't noticed that part of the patch.  But I don't
think that's needed.  Updating the times through the file pointer
should be OK.  You have this problem because you use the inode which
comes from the blockdev pseudo-filesystem.

> 
> > But I've moved the check from __fput to remove_vma() in the next
> > revision of the patch, which would give slightly nicer semantics, and
> > be equally conforming.
> 
> This still does not address the situation where a file is 'permanently'
> mmap'd, does it?

So?  If application doesn't do msync, then the file times won't be
updated.  That's allowed by the standard, and so portable applications
will have to call msync.

Thanks,
Miklos

--
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:[~2007-02-22 20:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21 17:51 Miklos Szeredi, Miklos Szeredi
2007-02-21 18:07 ` Peter Staubach
2007-02-21 18:23   ` Miklos Szeredi
2007-02-21 18:54     ` Peter Staubach
2007-02-21 19:07       ` Miklos Szeredi
2007-02-22 17:36         ` Peter Staubach
2007-02-22 18:16           ` Miklos Szeredi
2007-02-22 20:11             ` Peter Staubach
2007-02-22 20:43               ` Miklos Szeredi
2007-02-22 20:50                 ` Peter Staubach
2007-02-21 18:12 ` Trond Myklebust
2007-02-21 18:28   ` Miklos Szeredi
2007-02-21 18:36     ` Trond Myklebust
2007-02-21 18:50       ` Peter Staubach
2007-02-21 18:50       ` Miklos Szeredi
2007-02-22  4:26 ` Andrew Morton
2007-02-22  7:49   ` Miklos Szeredi
2007-02-22 17:39     ` Peter Staubach
2007-02-22 18:08       ` Miklos Szeredi
2007-02-22 20:14         ` Peter Staubach
2007-02-22 20:48           ` Miklos Szeredi [this message]
2007-02-22 20:55             ` Peter Staubach
2007-02-22 21:04             ` Trond Myklebust
2007-02-22 21:28               ` Miklos Szeredi
2007-02-22 21:52                 ` Peter Staubach
2007-02-22 22:08                   ` Miklos Szeredi

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=E1HKKrL-0006k6-00@dorka.pomaz.szeredi.hu \
    --to=miklos@szeredi.hu \
    --cc=akpm@linux-foundation.org \
    --cc=hugh@veritas.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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