linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@primarydata.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfs: update time staps on truncate
Date: Thu, 21 Aug 2014 11:31:24 -0400	[thread overview]
Message-ID: <CAHQdGtTniQYMUpOnKnG8H8W5WJsAysZA-FYCy1SHGOpFUebJBg@mail.gmail.com> (raw)
In-Reply-To: <1408633667-24177-1-git-send-email-hch@lst.de>

Hi Christoph,

On Thu, Aug 21, 2014 at 11:07 AM, Christoph Hellwig <hch@lst.de> wrote:
> 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;
> +               }
>         }
>

We shouldn't need to set attr->ia_ctime/ia_mtime above. We should set
the file time to the server clock time.
Also note that instead of checking attr->ia_size !=
i_size_read(inode), the above should check attr->ia_valid & ATTR_SIZE
due to the optimisation above.

-- 
Trond Myklebust

Linux NFS client maintainer, PrimaryData

trond.myklebust@primarydata.com

  reply	other threads:[~2014-08-21 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-21 15:07 [PATCH] nfs: update time staps on truncate Christoph Hellwig
2014-08-21 15:31 ` Trond Myklebust [this message]
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=CAHQdGtTniQYMUpOnKnG8H8W5WJsAysZA-FYCy1SHGOpFUebJBg@mail.gmail.com \
    --to=trond.myklebust@primarydata.com \
    --cc=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).