[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cifs-protocol
Subject:    Re: [cifs-protocol] [REG:119101421001093] MS-SMB2/FSA: File.LastModificationTime, update "lost" agai
From:       Ralph Boehme via cifs-protocol <cifs-protocol () lists ! samba ! org>
Date:       2019-12-09 15:58:27
Message-ID: aa4bd8bf-af50-ecb6-eef0-e05356d42c23 () samba ! org
[Download RAW message or body]

Am 11/5/19 um 5:26 PM schrieb Sreekanth Nadendla:
> Hello Ralph, in addition to the answer provided for the issue " 119101121001349 \
> MS-SMB2: File.LastModificationTime updates for write IO vs setinfo" I would like to \
> add the following to explain the behavior with approx 15ms delay. 
> This is simply because the API NTFS uses to query the current time \
> (KeQuerySystemTime) has a resolution of 15.625 ms, so when a smaller amount of time \
> than that has passed it's not necessarily detectable.

good heaves! :) Good to know that.

It would be extremely helpful to see this in MS-FSA mentioned as Winodws
implementation specific behaviour.

Thanks!
-slow

-- 
Ralph Boehme, Samba Team                https://samba.org/
Samba Developer, SerNet GmbH   https://sernet.de/en/samba/
GPG-Fingerprint   FAE2C6088A24252051C559E4AA1E9B7126399E46

_______________________________________________
cifs-protocol mailing list
cifs-protocol@lists.samba.org
https://lists.samba.org/mailman/listinfo/cifs-protocol


[prev in list] [next in list] [prev in thread] [next in thread]