[prev in list] [next in list] [prev in thread] [next in thread]
List: cifs-protocol
Subject: [cifs-protocol] New Case Created: 00744883
From: Modcloth Customer Care via cifs-protocol <cifs-protocol () lists ! samba ! org>
Date: 2019-10-02 14:33:10
Message-ID: m43PE000000000000000000000000000000000000000000000PYR4FA00MwiYLz5iQ4qbAvK8v2R6nA () sfdc ! net
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hey Stefan,
Thank you for writing to ModCloth Customer Care! We have received your message and \
hope to be getting back to you within 3 business days.
If you have an urgent need, you can always contact us with any questions, concerns or \
feedback via live chat by clicking here or by phone (888-495-9699) between the hours \
of 9am-9pm EST Monday-Friday, we're always more than happy to help! ?
Thanks,
Modcloth
Email Body:-
Dochelp in Bcc
Casemail in Cc
Hello Stefan, thank you for your inquiry about MS-SMB2 specification. We have created \
incident 119100224002125 to investigate this issue.
Regards,
Sreekanth Nadendla
Microsoft Windows Open Specifications
-----Original Message-----
From: Stefan Metzmacher <metze@samba.org>
Sent: Wednesday, October 2, 2019 10:19 AM
To: Interoperability Documentation Help <dochelp@microsoft.com>; Edgar Olougouna \
<edgaro@microsoft.com>; cifs-protocol@lists.samba.org
Subject: SMB3 LockSequence
Hi Edgar,
we discussed the topic in Redmond...
Even Windows Server 2019 only implements lock sequence checking only for resilient \
and persistent handles as a server. While its client side uses lock sequence checking \
if it negotiated multichannel with the server.
[MS-SMB2] 3.3.5.14 Receiving an SMB2 LOCK Request
...
If the LockSequence value in the SMB2 LOCK Request (section 2.2.26) is not zero, \
and either one of the following conditions is TRUE, the server SHOULD verify whether \
the lock/unlock request with that LockSequence value has been successfully processed \
before:
* Connection.Dialect is "2.1" and Open.IsResilient is TRUE.
* Connection.Dialect belongs to the SMB 3.x dialect family.<318>
...
<318> Section 3.3.5.14: Windows 8, Windows Server 2012, Windows 8.1,
and Windows Server 2012 R2 do not verify the LockSequence value
in the SMB2 LOCK Request (section 2.2.26) when both
Open.IsResilient and Open.IsPersistent are FALSE.
Note <318> also applies to Windows Server 2016 and 2019 (any current version).
It would be great if the documentation can be adjusted.
But the more important question would be that the Windows Server behavior will be \
changed to just use the SMB 3.x dialect to turn the LockSequence checking on. Would \
it be possible to get a commitment from Microsoft that this will be fixed in future \
releases? Backports would also be nice.
Thanks!
metze
_______________________________________________
cifs-protocol mailing list
cifs-protocol@lists.samba.org
https://lists.samba.org/mailman/listinfo/cifs-protocol
ref:_00D7F5lFYJ._5007FrqOrf:ref
Have more questions? We have the answers!
We're here 9am-9pm EST Monday-Friday to help inspire your unique personal style and \
help you feel like the most remarkable version of you!
Don't hesitate to connect with us through chat or email on our help page here, \
https://help.modcloth.com/, or call us at 888-495-9699.
[Attachment #5 (text/html)]
<html><style>p{margin-top:0px; margin-bottom:0px;}</style><body class="setupTab" \
style=" background-color:#CCCCCC; bEditID:b1st1; bLabel:body;"><center ><table \
cellpadding="0" width="500" cellspacing="0" id="topTable" height="450" ><tr \
valign="top" ><td style=" background-color:#FFFFFF; bEditID:r1st1; bLabel:header; \
vertical-align:top; height:100; text-align:left;"><img border="0" bEditID="r1sp1" \
bLabel="headerImage" id="r1sp1" \
src="https://modcloth.my.salesforce.com/servlet/servlet.ImageServer?id=0157F000001F96x&oid=00D7F000005lFYJ" \
></img></td></tr><tr valign="top" ><td style=" background-color:#AAAAFF; \
> bEditID:r2st1; bLabel:accent1; height:5;"></td></tr><tr valign="top" ><td \
> styleInsert="1" height="300" style=" background-color:#f2efea; bEditID:r3st1; \
> color:#000000; bLabel:main; font-size:12pt; font-family:arial;"><table border="0" \
> cellpadding="5" width="550" cellspacing="5" height="400" ><tr valign="top" \
> height="400" ><td tEditID="c1r1" style=" background-color:#f2efea; bEditID:r3st1; \
> color:#000000; bLabel:main; font-size:12pt; font-family:arial;" aEditID="c1r1" \
> locked="0" ><font face="arial" style="color: rgb(0, 0, 0); font-family: arial; \
> font-size: 12pt;"><span style="font-size: 12pt;">Hey \
> Stefan,</span></font><br><br><font face="arial" style="color: rgb(0, 0, 0); \
> font-family: arial; font-size: 12pt;"><span style="font-size: 12pt;">Thank you for \
> writing to ModCloth Customer Care! We have received your message and hope to be \
> getting back to you within 3 business days.</span></font><br><br><div style="color: \
> rgb(0, 0, 0); font-family: arial; font-size: 12pt;">If you have an urgent need, you \
> can always contact us with any questions, concerns or feedback via live chat by \
> clicking <a href="https://sforce.co/2vibwwH">here</a> or by phone \
> (888-495-9699) between the hours of 9am-9pm EST Monday-Friday, we're always more \
> than happy to help! 😊</div><div style="color: rgb(0, 0, 0); font-family: arial; \
> font-size: 12pt;"><br></div><div style="color: rgb(0, 0, 0); font-family: arial; \
> font-size: 12pt;">Thanks,</div><div style="color: rgb(0, 0, 0); font-family: arial; \
> font-size: 12pt;"><br></div><font face="arial" style="color: rgb(0, 0, 0); \
> font-family: arial; font-size: 12pt;"><span style="font-size: \
> 12pt;">Modcloth</span></font><br><font face="arial" style="color: rgb(0, 0, 0); \
> font-family: arial; font-size: 12pt;"><span style="font-size: 12pt;">Email \
> Body:-</span></font><br><font face="arial" style="color: rgb(0, 0, 0); font-family: \
> arial; font-size: 12pt;"><span style="font-size: 12pt;">Dochelp in Bcc<br>Casemail \
> in Cc<br><br>Hello Stefan, thank you for your inquiry about MS-SMB2 specification. \
> We have created incident 119100224002125 to investigate this issue. \
> <br><br>Regards,<br>Sreekanth Nadendla<br>Microsoft Windows Open \
> Specifications<br><br>-----Original Message-----<br>From: Stefan Metzmacher \
> <metze@samba.org> <br>Sent: Wednesday, October 2, 2019 10:19 AM<br>To: \
> Interoperability Documentation Help <dochelp@microsoft.com>; Edgar Olougouna \
> <edgaro@microsoft.com>; cifs-protocol@lists.samba.org<br>Subject: SMB3 \
> LockSequence<br><br>Hi Edgar,<br><br>we discussed the topic in \
> Redmond...<br><br>Even Windows Server 2019 only implements lock sequence checking \
> only for resilient and persistent handles as a server.<br>While its client side \
> uses lock sequence checking if it negotiated multichannel with the server.<br><br> \
> [MS-SMB2] 3.3.5.14 Receiving an SMB2 LOCK Request<br><br> ...<br><br> If the \
> LockSequence value in the SMB2 LOCK Request (section 2.2.26) is not zero, and \
> either one of the following conditions is TRUE, the server SHOULD verify whether \
> the lock/unlock request with that LockSequence value has been successfully \
> processed before:<br> * Connection.Dialect is "2.1" and Open.IsResilient \
> is TRUE.<br> * Connection.Dialect belongs to the SMB 3.x dialect \
> family.<318><br><br> ...<br><br> <318> Section 3.3.5.14: Windows 8, \
> Windows Server 2012, Windows 8.1,<br> and Windows Server 2012 R2 do not \
> verify the LockSequence value<br> in the SMB2 LOCK Request (section 2.2.26) \
> when both<br> Open.IsResilient and Open.IsPersistent are FALSE.<br><br>Note \
> <318> also applies to Windows Server 2016 and 2019 (any current \
> version).<br><br>It would be great if the documentation can be adjusted.<br><br>But \
> the more important question would be that the Windows Server behavior will be \
> changed to just use the SMB 3.x dialect to turn the LockSequence checking \
> on.<br>Would it be possible to get a commitment from Microsoft that this will be \
> fixed in future releases?<br>Backports would also be \
> nice.<br><br>Thanks!<br>metze<br><br>_______________________________________________<br>cifs-protocol \
> mailing list<br>cifs-protocol@lists.samba.org<br>https://lists.samba.org/mailman/listinfo/cifs-protocol</span></font><div \
> style="color: rgb(0, 0, 0); font-family: arial; font-size: 12pt;"><br></div><div \
> style=""><font face="arial">ref:_00D7F5lFYJ._5007FrqOrf:ref</font></div></td></tr></table></td></tr><tr \
> valign="top" style=" display:none;"><td style=" background-color:#ffffff; \
> bEditID:r4st1; bLabel:accent2; height:0;"></td></tr><tr valign="top" style=" \
> display:none;"><td style=" background-color:#FFFFFF; bEditID:r5st1; bLabel:footer; \
> vertical-align:; height:0; text-align:;"></td></tr><tr valign="top" style=" \
> display:none;"><td style=" background-color:#AAAAFF; bEditID:r6st1; \
> bLabel:accent3; height:0;"></td></tr></table></center><img \
> src="http://modcloth.my.salesforce.com/servlet/servlet.ImageServer?oid=00D7F000005lFYJ&esid=0187F00000Dov9m"></body></html><br><br>Have \
> more questions? We have the answers!
<br>
<br>We're here 9am-9pm EST Monday-Friday to help inspire your unique personal style \
and help you feel like the most remarkable version of you! <br>
<br>Don't hesitate to connect with us through chat or email on our help page here, <A \
HREF="https://help.modcloth.com" TARGET="_blank">https://help.modcloth.com</A>/, or \
call us at 888-495-9699.
_______________________________________________
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