Dochelp in Bcc Casemail in Cc Hello Ralph, I will be assisting you with your question. I am currently researching the problem and will provide you with an update soon. Thank you for your patience.
Regards, Sreekanth Nadendla Microsoft Windows Open Specifications -----Original Message----- From: Ralph Boehme <[email protected]> Sent: Wednesday, December 11, 2019 1:50 AM To: Interoperability Documentation Help <[email protected]> Cc: [email protected] Subject: [EXTERNAL] [MS-FSA] Setting end-of-file on file-handle with pending delayed write-time update Hello dochelp! Note: the following only applies to Windows versions where the SMB server implements delayed write-time updates. I've verified that the behaviour described below is reproducible against the following Windows versions: Windows 7, Windows 2008r2 and Windows 2016. With Windows 2019 I see a different behaviour, which is as expected, as it implements immediate timestamp updates. SMB2 scenario: 1) create file -> file handle H1 2) sleep one second 3) write one byte to H1 4) getinfo on H1 -> write-time hasn't been updated, delayed update still pending 5) setinfo end-of-file with size=1 on H1 (so existing size = requested new size) 6) getinfo again on H1 -> now the write-time has been updated This is the behaviour that is reproducible against Windows 7, Windows 2008r2, Windows 2016, but not Windows 2019. Apparently, the setinfo in step 5 flushed the pending write-time update. Question: as the legacy delayed write-time handling is not (was never?) documented in MS-FSA, I'm asking for confirmation that the following conclusion is correct: * a setinfo-eof on a file-handle flushes pending write-time updates * flush happens even if the requested size equals the existing size If this is correct, are there other operations that trigger this behaviour? pcap: <https://nam06.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.samba.org%2F~slow%2Fpcaps%2Fbug14150.pcapng.gz&data=02%7C01%7Csrenaden%40microsoft.com%7Cbc697f25c8234a79223708d77e06660b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637116438260754970&sdata=4xPCL7XindNk%2B%2FSS4HHa5fmi12Mga8g4Y6KAz5TkfsI%3D&reserved=0> For completenes, here's also a pcap against Windows 2019: <https://nam06.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.samba.org%2F~slow%2Fpcaps%2Fbug14150-w2019.pcapng.gz&data=02%7C01%7Csrenaden%40microsoft.com%7Cbc697f25c8234a79223708d77e06660b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637116438260754970&sdata=5wWjHnaLWVy0Hqykl%2Fyz0dBxglt3VBJlRnfHyzJsIlE%3D&reserved=0> This one stops at step 4 when the client test driver detects that write-time did already change. Thanks! -slow -- Ralph Boehme, Samba Team https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsamba.org%2F&data=02%7C01%7Csrenaden%40microsoft.com%7Cbc697f25c8234a79223708d77e06660b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637116438260764964&sdata=mXCjMztDUwhKFSxcH%2BSoreyDXoXNCbtzmpakBzDxyfM%3D&reserved=0 Samba Developer, SerNet GmbH https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsernet.de%2Fen%2Fsamba%2F&data=02%7C01%7Csrenaden%40microsoft.com%7Cbc697f25c8234a79223708d77e06660b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637116438260764964&sdata=HiPThHlFH25RgCvk%2BPTnPYMKcek%2FJPGrZNbBpt88LEs%3D&reserved=0 GPG-Fingerprint FAE2C6088A24252051C559E4AA1E9B7126399E46 _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
