[linux-cifs-client] timestamp problems with cp -p

[Steve French]

>  kukks: smfrench: the needed "sleep 1" in "stat localfile && cp -p localfile /mnt && sleep 1 && stat /mnt/localfile" is also a bit strange
The 1 second timeout is needed since the local cache of the inode
timestamps is kept for 1 second ... (and the write and setattr were in
the correct order locally but the incorrect order remotely - so when
we revalidated the cached inode it was wrong - the local copy of the
timestamps would probably be fine as long as the file was open and
oplocked)

> kukks: smfrench: i had already posted another solution on the cifs mailing list for inode.c ---> cifs_setattr(), which is not patching cifs_unlink atm, where the same sequence for setpathinfo/setfileinfo is used.

What is this issue? utimes itself fails to Windows when file open? I
see http://rafb.net/p/0bzb2Y13.html but I don't recognize the high
level problem.  Will trace it to Windows tomorrow.


-- 
Thanks,

Steve