Subject: Re: [BUG] NFS no longer updates file modification times
	appropriately
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: joe.korty@ccur.com
Cc: linux-kernel@vger.kernel.org, Ronny.Lampert@telecasystems.de,
       ioe-lkml@rameria.de
In-Reply-To: <20040607161304.GA22505@tsunami.ccur.com>
References: <1086623509.4173.7.camel@lade.trondhjem.org>
	 <20040607161304.GA22505@tsunami.ccur.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT
Message-Id: <1086625209.4597.0.camel@lade.trondhjem.org>
Mime-Version: 1.0
Date: Mon, 07 Jun 2004 12:20:11 -0400
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 798
Lines: 21

P? m? , 07/06/2004 klokka 12:13, skreiv Joe Korty:
> > 
> > >   In which case we
> > > could defer a timestamp-on-write only when it is still in the same second
> > > as the previous write, but don't defer when a new second rolls around
> > > on the client.  That would reduce timestamp updates to at most one per
> > > second per inode per client, while preserving old NFS behavior.
> > 
> > Exactly why should we go to all this trouble?
> 
> For compatibility?

With what? There has never been a standard other than the close-to-open.

Cheers,
  Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/