From: Christoph Hellwig <hch@lst.de>
To: linux-nfs@vger.kernel.org
Subject: [PATCH] nfs: update time staps on truncate
Date: Thu, 21 Aug 2014 10:07:47 -0500 [thread overview]
Message-ID: <1408633667-24177-1-git-send-email-hch@lst.de> (raw)
The VFS handles attributes on truncate in a strange way, fix NFS to handle
it properly by copying a small code sniplet from XFS.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
fs/nfs/inode.c | 22 +++++++++++++++++++++-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/fs/nfs/inode.c b/fs/nfs/inode.c
index 577a36f..5bbd991 100644
--- a/fs/nfs/inode.c
+++ b/fs/nfs/inode.c
@@ -505,8 +505,28 @@ nfs_setattr(struct dentry *dentry, struct iattr *attr)
attr->ia_valid &= ~ATTR_MODE;
if (attr->ia_valid & ATTR_SIZE) {
- if (!S_ISREG(inode->i_mode) || attr->ia_size == i_size_read(inode))
+ if (!S_ISREG(inode->i_mode) ||
+ attr->ia_size == i_size_read(inode))
attr->ia_valid &= ~ATTR_SIZE;
+
+ /*
+ * Only change the c/mtime if we are changing the size or we
+ * are explicitly asked to change it. This handles the
+ * semantic difference between truncate() and ftruncate() as
+ * implemented in the VFS.
+ *
+ * The regular truncate() case without ATTR_CTIME and
+ * ATTR_MTIME is a special case where we need to update the
+ * times despite not having these flags set. For all other
+ * operations the VFS set these flags explicitly if it wants
+ * a timestamp update.
+ */
+ if (attr->ia_size != i_size_read(inode) &&
+ !(attr->ia_valid & (ATTR_CTIME | ATTR_MTIME))) {
+ attr->ia_ctime = attr->ia_mtime =
+ current_fs_time(inode->i_sb);
+ attr->ia_valid |= ATTR_CTIME | ATTR_MTIME;
+ }
}
/* Optimization: if the end result is no change, don't RPC */
--
1.9.1
next reply other threads:[~2014-08-21 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 15:07 Christoph Hellwig [this message]
2014-08-21 15:31 ` [PATCH] nfs: update time staps on truncate Trond Myklebust
2014-09-06 23:28 ` 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=1408633667-24177-1-git-send-email-hch@lst.de \
--to=hch@lst.de \
--cc=linux-nfs@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).