From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Chow <davidchow@shaolinmicro.com>
Subject: Re: Problems of lookup_revalidate
Date: Thu, 29 Aug 2002 17:26:32 +0800
Sender: linux-fsdevel-owner@vger.kernel.org
Message-ID: <3D6DE8C8.3080601@shaolinmicro.com>
References: <3D6A4EF2.1070607@shaolinmicro.com>	<200208261810.37180.trond.myklebust@fys.uio.no>	<3D6AD750.2070602@shaolinmicro.com> <shsznv8npw5.fsf@charged.uio.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: linux-fsdevel@vger.kernel.org
Return-path: <linux-fsdevel-owner@vger.kernel.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
List-Id: linux-fsdevel.vger.kernel.org

Trond Myklebust wrote:

>>>>>>" " == David Chow <davidchow@shaolinmicro.com> writes:
>>>>>>            
>>>>>>
>
>     > Even I cat the file, the file seems still using the old cache
>     > on the client, but the server version has changed. Any
>     > possibilities? The mtime and size of the file at the server HAS
>     > changed so why not nfs client refresh_inode() on openning the
>     > file?
>
>That should normally not happen. Are you also updating ctime properly
>on the server when you change the mtime/size?
>
>Cheers,
>  Trond
>  
>
Of course the ctime has changed because the file is edited and saved at 
the server. The problem is it is not close-to-open in this case. I 
notice dir.c has some change in lookup_revalidate(), whats the purpose 
of the change from 2.4.18 to 2.4.19? I have no problem in 2.4.18 .

David