<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle22
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=Section1><p class=MsoNormal><span style='color:#1F497D'>Hi Steven,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thank you for your email.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Someone from my team will be working with you and will be contacting you tomorrow.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thanks and regards,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><p class=MsoNormal><b><span style='font-size:12.0pt;font-family:"Arial","sans-serif";color:black'>Sebastian Canevari</span></b><span style='font-size:12.0pt;color:navy'><br></span><span style='font-family:"Arial","sans-serif";color:black'>Senior Support Escalation Engineer, US-CSS&nbsp;DSC PROTOCOL TEAM</span><span style='color:navy'><br></span><span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:black'>7100 N Hwy 161, Irving, TX - 75039</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:black'>&quot;Las Colinas - LC2&quot;<o:p></o:p></span></p><p class=MsoNormal><i><span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:black'>Tel: +1 469 775 7849<o:p></o:p></span></i></p><p class=MsoNormal style='margin-bottom:12.0pt'><i><span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:black'><a href="mailto:sebastc@microsoft.com">e-mail: sebastc@microsoft.com</a></span></i><span style='color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Steven Danneman [mailto:steven.danneman@isilon.com] <br><b>Sent:</b> Monday, November 30, 2009 5:58 PM<br><b>To:</b> Interoperability Documentation Help; cifs-protocol@samba.org; pfif@tridgell.net<br><b>Subject:</b> SMB2 mixed lock &amp; unlock requests in a single SMB_LOCK request<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Hello,<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>I&#8217;ve come across another SMB2 locking issue that I can&#8217;t find explicit documentation for in MS-SMB2 (v18.0).<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>My first question, is whether a single SMB_LOCK request can contain both unlock and lock requests as the LockingAndX command type in SMBv1 could?&nbsp; The MS-SMB2 document hints that the answer to this question is &#8220;no&#8221; but it doesn&#8217;t seem to explicitly state it anywhere.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Section 2.2.26 states: &#8220;The SMB2 LOCK Request packet is sent by the client to either lock or unlock portions of a file.&#8221; <o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>This statement is ambiguous as to whether the &#8220;or&#8221; is inclusive or exclusive.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>In my testing, sending both lock and unlock requests in a single SMB2 locking request returns a STATUS_INVALID_PARAMETER.&nbsp; However, if the requests are ordered such that a unlock structure come first, the unlock request seems to succeed.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>The attached pcap, against W2K8R2 shows:<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>1) Packet 27-28: &nbsp;A single lock request succeeding on range 0-10.<o:p></o:p></p><p class=MsoNormal>2) Packet 29-30: &nbsp;A lock request with unlock(0-10) and lock(10-10) failing with INVALID_PARAMETER.<o:p></o:p></p><p class=MsoNormal>3) Packet 31-32:&nbsp; A lock request with lock(0-10) and lock(10-10) succeeding, showing that the previous request, though it returned an error, succeeded in unlocking.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>It seems to me the server behavior should be to return STATUS_INVALID_PARAMETER without completing any of the lock/unlock requests when they are mixed.&nbsp; Both the fact that this isn&#8217;t allowed, and the W2K8R2 behavior deviation should be documented.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Steven Danneman</span></b><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#666666'>&nbsp;</span></b><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#2676AE'>|</span></b><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#666666'>&nbsp;<strong><span style='font-family:"Arial","sans-serif"'>Software Development Engineer</span></strong><br></span></b><b><span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:black'>Isilon Systems</span></b><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#666666'>&nbsp;&nbsp;&nbsp; P </span></b><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:black'>+1-206-315-7500</span></b><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#666666'>&nbsp;</span></b><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#666666'>&nbsp;&nbsp;&nbsp; F&nbsp; </span></b><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:black'>+1-206-315-7501</span></b><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#666666'><br></span></b><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#003366'><a href="http://www.isilon.com">www.isilon.com</a></span></b><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#666666'>&nbsp;</span></b><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#666666'> &nbsp;</span></b><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#666666'>&nbsp;</span></b><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:black'>&nbsp;</span></b><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#666666'>&nbsp;&nbsp;</span></b><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#666666'>&nbsp;</span></b><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#666666'><o:p></o:p></span></b></p><p style='vertical-align:middle'><span style='color:navy'><img border=0 width=82 height=46 id="Picture_x0020_1" src="cid:image001.gif@01CA720C.69080DF0" alt="cid:image001.gif@01C81005.1792D9C0">&nbsp;</span><b><span style='color:#666666'>&nbsp;&nbsp;</span></b><strong><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#666666'>How breakthroughs begin. &#8482;</span></strong><o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p></div></body></html>