From: Rob Sims <lkml-z@robsims.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Change in NFS client behavior
Date: Wed, 7 Sep 2005 08:25:36 -0600 [thread overview]
Message-ID: <20050907142536.GA26255@robsims.com> (raw)
In-Reply-To: <1125634747.8635.17.camel@lade.trondhjem.org>
On Fri, Sep 02, 2005 at 12:19:07AM -0400, Trond Myklebust wrote:
> fr den 02.09.2005 Klokka 00:15 (-0400) skreiv Trond Myklebust:
>
> > Sure. The other problem is that the test is made before the i_sem is
> > grabbed. OK, so how about the appended patch instead?
>
> Doh!
>
> Trond
> VFS/NFS: Fix up behaviour w.r.t. truncate() and open(O_TRUNC)
>
> POSIX and the SUSv3 specify that open(O_TRUNC) should always bump ctime/mtime
> whereas truncate() should only do so if the file size actually changes.
>
> Fix the behaviour of NFS, which currently is broken w.r.t. open(), and fix
> the VFS truncate() so that it no enforces the POSIX rules.
>
> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
> ---
> attr.c | 14 +++-----------
> nfs/inode.c | 5 -----
> open.c | 25 +++++++++++++++++++++++--
> 3 files changed, 26 insertions(+), 18 deletions(-)
This patch does not fix the original issue - timestamps are not updated
as expected.
--
Rob
next prev parent reply other threads:[~2005-09-07 14:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 14:55 Change in NFS client behavior Rob Sims
2005-09-01 23:38 ` Trond Myklebust
2005-09-02 3:43 ` Trond Myklebust
2005-09-02 3:45 ` Andrew Morton
2005-09-02 3:52 ` Trond Myklebust
2005-09-02 4:07 ` Andrew Morton
2005-09-02 4:15 ` Trond Myklebust
2005-09-02 4:19 ` Trond Myklebust
2005-09-02 4:38 ` Andrew Morton
2005-09-07 14:25 ` Rob Sims [this message]
2005-09-02 15:39 ` Rob Sims
2005-09-02 15:06 ` Drop NFS speed on move from kernel 2.4 to 2.6 (was: Change in NFS client behavior) Tomasz Kłoczko
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=20050907142536.GA26255@robsims.com \
--to=lkml-z@robsims.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.