[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: Sreekanth Nadendla via cifs-protocol <cifs-protocol () lists ! samba ! org>
Date: 2019-10-29 18:03:00
Message-ID: BL0PR2101MB0931330518C94819C3D030FFC5610 () BL0PR2101MB0931 ! namprd21 ! prod ! outlook ! com
[Download RAW message or body]
Hello Ralph, I just wanted to let you know that we are still researching this issue. \
I will update you as soon as I have the information to share with you.
Regards,
Sreekanth Nadendla
Microsoft Windows Open Specifications
-----Original Message-----
From: Jeff McCashland <jeffm@microsoft.com>
Sent: Mon, October 14, 2019 4:22 PM
To: Ralph Boehme <slow@samba.org>
Cc: cifs-protocol@lists.samba.org; support <support@mail.support.microsoft.com>; \
Sreekanth Nadendla <srenaden@microsoft.com>
Subject: RE: [REG:119101421001093] MS-SMB2/FSA: File.LastModificationTime, update \
"lost" against Windows 2019
+Sreekanth for collaboration
-----Original Message-----
From: Jeff McCashland
Sent: Monday, October 14, 2019 11:05 AM
To: Ralph Boehme <slow@samba.org>
Cc: cifs-protocol@lists.samba.org; support <support@mail.support.microsoft.com>
Subject: RE: [REG:119101421001093] MS-SMB2/FSA: File.LastModificationTime, update \
"lost" against Windows 2019
[Bryan to BCC]
Hi Ralph,
I will research your question, and also touch bases with Sreekanth regarding related \
SR 119101121001349.
I will let you know what I find.
Best regards,
Jeff McCashland | Senior Escalation Engineer | Microsoft Protocol Open Specifications \
Team
Phone: +1 (425) 703-8300 x38300 | Hours: 9am-5pm | Time zone: (UTC-08:00) Pacific \
Time (US and Canada) Local country phone number found here: \
https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsupport.microsoft.com \
%2Fglobalenglish&data=02%7C01%7Csrenaden%40microsoft.com%7C75fbb0e759b74d64684508d \
750e4255d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637066813120276402&sdata=mrs0CA7CgXiCp62MnPGhKeYAtNzNNTUc1aL4O34kfEE%3D&reserved=0 \
| Extension 1138300 We value your feedback. My manager is Jeremy Chapman (jeremyc), \
+1 (469) 775-2475
-----Original Message-----
From: Bryan Burgin <bburgin@microsoft.com>
Sent: Monday, October 14, 2019 10:09 AM
To: Ralph Boehme <slow@samba.org>
Cc: cifs-protocol@lists.samba.org; support <support@mail.support.microsoft.com>
Subject: [REG:119101421001093] MS-SMB2/FSA: File.LastModificationTime, update "lost" \
against Windows 2019
[-Dochelp to bcc]
[+Support]
Hi Ralph,
Thank you for your question. We created SR 119101421001093 to track your issue. An \
engineer from the protocols team will contact you soon.
Bryan
-----Original Message-----
From: Ralph Boehme <slow@samba.org>
Sent: Monday, October 14, 2019 9:57 AM
To: Interoperability Documentation Help <dochelp@microsoft.com>
Cc: cifs-protocol@lists.samba.org
Subject: MS-SMB2/FSA: File.LastModificationTime, update "lost" against Windows 2019
Hello dochelp,
I'm seeking clarification with regard to behaviour of MS-FSA \
File.LastModificationTime over SMB2.
Scenario
========
A) SMB client creates testfile -> handle H1
B) Client queries LastModificationTime with SMB2 GETINFO
C) Client writes to handle H1
D) 1 s delay
E) Close H1 with SMB2_CLOSE_FLAG_POSTQUERY_ATTRIB set
F) Re-open testfile, query timestamps, close (just to verify values from close \
response from step E).
Results
=======
Against a Windows 2016 server the testfile's modification time is updated in step E \
(packet 32) compared to the time from step B.
<https://nam06.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.samba.org%2F~slow% \
2Fpcaps%2Fw2016-smb2-create-delay-getinfo-write-close.pcapng&data=02%7C01%7Csrenad \
en%40microsoft.com%7C75fbb0e759b74d64684508d750e4255d%7C72f988bf86f141af91ab2d7cd011db \
47%7C1%7C0%7C637066813120276402&sdata=WyES0QXsNDPRwsMCPqg7suGk8mArEuKeiYd0uGVSvw0%3D&reserved=0>
Against a Windows 2019 server the testfile's modification time remains unmodified \
across steps E and F compared to step B (packets 80+94). In other words: the write \
didn't trigger any update to File.LastModificationTime.
<https://nam06.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.samba.org%2F~slow% \
2Fpcaps%2Fw2019-smb2-create-delay-getinfo-write-close.pcapng&data=02%7C01%7Csrenad \
en%40microsoft.com%7C75fbb0e759b74d64684508d750e4255d%7C72f988bf86f141af91ab2d7cd011db \
47%7C1%7C0%7C637066813120276402&sdata=Bm6v4R3zN2Be06Hr882K6qBgo5gf%2F2nRXc%2FZz0%2BE%2Ba4%3D&reserved=0>
I'm trying to figure out what's changed wrt File.LastModificationTime between Windows \
2003, from which Samba's behaviour was derived, and Window 2019 and so far all this \
doesn't make sense.
The scenario in this case is also dependent on the time between step A and B (none is \
this example above). It seems if the time between A and B is bigger then a certain \
threshold of ~15 ms, then the behaviour changes and we see an immediate update of the \
timestamp in step B (packet 80):
<https://nam06.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.samba.org%2F~slow% \
2Fpcaps%2Fw2019-smb2-create-delay-15ms-getinfo-write-close.pcapng&data=02%7C01%7Cs \
renaden%40microsoft.com%7C75fbb0e759b74d64684508d750e4255d%7C72f988bf86f141af91ab2d7cd \
011db47%7C1%7C0%7C637066813120276402&sdata=dPtBA7Xu39wsY4jyaUQe5BLWBVNJtUIs6c%2Fl6zA7SNM%3D&reserved=0>
Cf case 119101121001349 for another related question.
Questions
=========
Is this behaviour documented somewhere? It would be good to get \
File.LastModificationTime (plus friends) behaviour documented across the full set of \
affecting operations.
I have further observations and traces from more complex scenarios, but I'm trying to \
come up with the most simple one and later expand on that. :)
Thanks!
-slow
--
Ralph Boehme, Samba Team \
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsamba.org%2F&dat \
a=02%7C01%7Csrenaden%40microsoft.com%7C75fbb0e759b74d64684508d750e4255d%7C72f988bf86f1 \
41af91ab2d7cd011db47%7C1%7C0%7C637066813120276402&sdata=%2FcwZJnVkqcZ9oZdN0WfhPbGgFdMUVn%2FJkAkdKPDRyfs%3D&reserved=0
Samba Developer, SerNet GmbH \
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsernet.de%2Fen%2Fsam \
ba%2F&data=02%7C01%7Csrenaden%40microsoft.com%7C75fbb0e759b74d64684508d750e4255d%7 \
C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637066813120276402&sdata=vm9wK8o6WM%2BDKTUYWr3eO036K%2FRFvirRQvWKl6A6Q0k%3D&reserved=0
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic