<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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 12 (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: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.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@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="2050" />
</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>Hello,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>When requesting a byte-range lock over SMBv1 on a range of a
file which is already locked and thus will contend, the error code returned is inconsistent.
The first attempt to acquire a held lock will return STATUS_LOCK_NOT_GRANTED.
Subsequent requests will return STATUS_FILE_LOCK_CONFLICT.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>This seems as though it may be an error in the
implementation of the SMBv1 protocol as the explanation of the two errors in
MS-ERREF implies that STATUS_LOCK_NOT_GRANTED should always be returned in this
circumstance:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>STATUS_LOCK_NOT_GRANTED
A requested file lock cannot be granted due to other existing locks.<o:p></o:p></p>
<p class=MsoNormal>STATUS_FILE_LOCK_CONFLICT A
requested read/write cannot be granted due to a conflicting file lock.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>And in this same scenario the SMBv2 protocol always returns
STATUS_LOCK_NOT_GRANTED.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I aware this is a well known issue, as the Samba torture
test demonstrating this behavior have existed for a number of years, but I
haven’t found any Microsoft documentation describing the semantics of
this behavior. I’ve looked in MS-CIFS, MS-SMB, MS-SMB2, and MS-FSA.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Furthermore, which error code is returned becomes even more
complicated when additional lock requests are interspersed. For example
the attached pcap against a W2K8R2 server shows:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>1) Two file handles opened to the same file 0x400b, 0x400c<o:p></o:p></p>
<p class=MsoNormal>2) Packet 27,28: Handle 0x400b successfully acquiring an
exclusive lock on range 100 – 110<o:p></o:p></p>
<p class=MsoNormal>3) Packet 29-32: Handles 0x400b and 0x400c requesting the
same held range and receiving STATUS_LOCK_NOT_GRANTED<o:p></o:p></p>
<p class=MsoNormal>4) Packet 33-44: Again requesting the same held range and
receiving STATUS_FILE_LOCK_CONFLICT<o:p></o:p></p>
<p class=MsoNormal>5) Packet 45-54: Requesting a lock on an overlapping range,
105-115, and receiving the same pattern of errors<o:p></o:p></p>
<p class=MsoNormal>6) Packet 55-64: Requesting a lock on the previous range,
100-110, and now having the response be “reset” back to
STATUS_LOCK_NOT_GRANTED<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I’d like to have some documentation of the algorithm
for determining which error to return based on the state of existing locks, or
history of previously requested locks.<o:p></o:p></p>
<p class=MsoNormal><o:p> </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'> </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'> <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'> 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'> </span></b><b><span
style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#666666'>
F </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'> </span></b><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#666666'> </span></b><b><span
style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#666666'> </span></b><b><span
style='font-size:7.5pt;font-family:"Arial","sans-serif";color:black'> </span></b><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#666666'> </span></b><b><span
style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#666666'> </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@01CA6DE7.92263190"
alt="cid:image001.gif@01C81005.1792D9C0"></span><span style='color:navy'> </span><b><span
style='color:#666666'> </span></b><strong><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:#666666'>How breakthroughs begin.
™</span></strong><o:p></o:p></p>
</div>
</body>
</html>