public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Peter Staubach <staubach@redhat.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	Neil Brown <neilb@suse.de>, NFS List <nfs@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [NFS] [PATCH] NFS server does not update mtime on setattr	request
Date: Wed, 07 Jun 2006 13:17:03 -0400	[thread overview]
Message-ID: <1149700624.26188.15.camel@localhost> (raw)
In-Reply-To: <4486F479.90406@redhat.com>

On Wed, 2006-06-07 at 11:44 -0400, Peter Staubach wrote:

> I am curious about how this would break truncate?

According to SuSv43, truncate should result in changes to
mtime/ctime/suid/sgid if and only if the file size changes. The
combination of disabling the client caching and always setting
mtime/ctime on the server will therefore clearly break truncate.

Cheers,
  Trond


  reply	other threads:[~2006-06-07 17:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 18:05 [PATCH] NFS server does not update mtime on setattr request Peter Staubach
2006-06-07  5:38 ` Trond Myklebust
2006-06-07 14:44   ` Peter Staubach
2006-06-07 15:17     ` [NFS] " J. Bruce Fields
2006-06-07 15:26       ` Peter Staubach
2006-06-07 15:39         ` Trond Myklebust
2006-06-07 15:44           ` Peter Staubach
2006-06-07 17:17             ` Trond Myklebust [this message]
2006-06-07 17:41               ` Peter Staubach
2006-06-07 15:42         ` J. Bruce Fields
2006-06-07 15:50           ` Peter Staubach
2006-06-07 16:03             ` J. Bruce Fields
2006-06-07 16:56               ` Peter Staubach
2006-06-09  0:40     ` Neil Brown
2006-06-09 13:10       ` Peter Staubach

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=1149700624.26188.15.camel@localhost \
    --to=trond.myklebust@fys.uio.no \
    --cc=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    --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