> Summary:
>
> The smbfs in kernel 2.0.31-33 causes serious corruption of file
> modification times of files on NT 4.0 (SP1/SP3) workstations & servers:
>
> 1) Opening a file for reading via smbfs (and closing it) corrupts the
> mtime as seen locally on NT!
>
> 2) Listing (stat'ing) a _file_ via smbfs returns a bogus mtime,
> but does not propagate it.
>
> 3) Listing a _directory_ (with e.g. ls(1)) returns the correct NT
> mtimes. Of course, if Linux have previously corrupted the NT file,
> NT will dutifully return the bogus mtime in the new listing too.
>
> Windows NT 3.51 (SP0/SP5) is not affected. Don't know about Win95.
>
> A preliminary patch at the end of this mail fixes the problem, provided
So far it looks like the patch works for me. I haven't tested it
extensively yet, but there were a couple of cases where I could
reliably produce date/time corruption and with my patched kernel
it would not corrupt.
What happened in 2.0.31 that introduced this problem?
Thank you very much,
Eric Hoeltzel