[linux-cifs-client] Hello, and possible problem (stale client -side cache)

[Vince Negri]

I wrote:

> 5) However, a command like "vi foo.c" ends up loading a file
> with the *old data* but the *new length*. If the file has been
> shortened on the server, one usually gets binary zeroes on the end
> of the file.

FYI I've now tracked down in more detail what triggers
the problem. 

An invocation of "make" with no arguments triggers a
scan of the current directory, which ends up updating
the timestamps and filesize in the inode *without*
invalidating the cache. I haven't worked out exactly
how this happens yet because the code seems to be dealing
with tmp_inode's.

As a contrast, "make -f Makefile", which does not need
to search in the currect directory, does not trigger the
bug.

I'll capture a cifsFYI log and post relevant portions if
anyone is interested.

Vince


Legal Disclaimer: Any views expressed by the sender of this message are
not necessarily those of Application Solutions Ltd. Information in this 
e-mail may be confidential and is for the use of the intended recipient
only, no mistake in transmission is intended to waive or compromise such 
privilege. Please advise the sender if you receive this e-mail by mistake.