From: Christoph Hellwig <hch@lst.de>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Christoph Hellwig <hch@lst.de>,
akpm@osdl.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] add some notes on file_update_time
Date: Fri, 11 Nov 2005 00:45:27 +0100 [thread overview]
Message-ID: <20051110234527.GC19418@lst.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0511102339290.24857@hermes-1.csi.cam.ac.uk>
> Nice explanation except for the last sentence. Surely you do not expect
> filesystem drivers to call notify_change()? I thought you told me that I
> should be setting the c/mtime directly, rather than using a function, so
> now you are going back on that? Or am I simply misunderstanding the
> sentence completely? I apologize if that is the case...
this was meant for non-fs callers. but to be there's no reason
why non-fs callers should look at this function in the first time.
The updated patch below just drop the sentence. we might want to write
up rules on c/mtime updates somewhere, but that's really not related to
file_update_time.
Index: linux-2.6/fs/inode.c
===================================================================
--- linux-2.6.orig/fs/inode.c 2005-11-10 16:02:18.000000000 +0100
+++ linux-2.6/fs/inode.c 2005-11-10 16:04:25.000000000 +0100
@@ -1208,7 +1208,11 @@
* @file: file accessed
*
* Update the mtime and ctime members of an inode and mark the inode
- * for writeback.
+ * for writeback. Note that this function is meant exclusively for
+ * usage in the file write path of filesystems, and filesystems may
+ * chose to explicitly ignore update via this function with the
+ * S_NOCTIME inode flag, e.g. for network filesystem where these
+ * timestamps are handled by the server.
*/
void file_update_time(struct file *file)
next prev parent reply other threads:[~2005-11-10 23:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 23:38 [PATCH] add some notes on file_update_time Christoph Hellwig
2005-11-10 23:41 ` Anton Altaparmakov
2005-11-10 23:45 ` Christoph Hellwig [this message]
2005-11-10 23:47 ` Christoph Hellwig
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=20051110234527.GC19418@lst.de \
--to=hch@lst.de \
--cc=aia21@cam.ac.uk \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).