lkml.org 
[lkml]   [2003]   [Feb]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: 2.4 iget5_locked port attempt to 2.4 (supposedly fixed NFS version this time)
From
>>>>> " " == Oleg Drokin <green@namesys.com> writes:

> Original patch was from Jan Harkes <jaharkes@cs.cmu.edu>,
> and was applied somewhere at the beginning of 2.5
> development. It still would be nice if someone more
> knowledgeable in NFS client code will review the changes
> (and the same is true for Coda of course).

Please remind me. Why can't NFS set inode->i_mode, call
nfs_fill_inode() etc. in the 'init_locked' callback?

As for the issue of the stat() problem you mentioned: does your server
have a monotonically increasing inode->i_ctime? If ntp or something
like that keeps turning the clock backward on the server, then the NFS
client has no chance of recognizing which attribute updates are the
more recent ones.

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/

\
 
 \ /
  Last update: 2005-03-22 13:33    [W:0.134 / U:1.828 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site