[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-fsdevel
Subject:    Re: i_size: why get complicated?
From:       Trond Myklebust <trond.myklebust () fys ! uio ! no>
Date:       2001-03-15 17:56:45
[Download RAW message or body]

>>>>> " " == Daniel Phillips <phillips@innominate.de> writes:

     > On Thu, 15 Mar 2001, Trond Myklebust wrote:
    >> >>>>> " " == Daniel Phillips <phillips@innominate.de> writes:
    >>
    >> > Only file_write, truncate and high level filesystem code code
    >> > should set i_size.
    >>
    >> That's only true for local filesystems. Networked filesystems
    >> can decide to set i_size at any time, since the server is the
    >> ultimate authority on a file's status and attributes.

     > Aren't you just agreeing with what I said: the high level
     > application (NFS in this case) should set the i_size, not
     > ->commit_write.

Ah sorry. Your use of 'high level' confused me: I tend to think of the
VFS in those terms.

In that case I think NFS at least could live with those rules.

Cheers,
  Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org

[prev in list] [next in list] [prev in thread] [next in thread]