[cifs-protocol] SMBv1 multiple lock cancel behavior
Sebastian.Canevari at microsoft.com
Thu Dec 3 16:24:50 MST 2009
Thanks for your inquiry.
Someone from my team will be contacting you shortly.
Thanks and regards,
Senior Support Escalation Engineer, US-CSS DSC PROTOCOL TEAM
7100 N Hwy 161, Irving, TX - 75039
"Las Colinas - LC2"
Tel: +1 469 775 7849
e-mail: sebastc at microsoft.com<mailto:sebastc at microsoft.com>
From: Steven Danneman [mailto:steven.danneman at isilon.com]
Sent: Thursday, December 03, 2009 4:57 PM
To: Interoperability Documentation Help
Cc: cifs-protocol at samba.org; pfif at tridgell.net
Subject: SMBv1 multiple lock cancel behavior
I've got yet another byte range locking question.
MS-CIFS (v0.1) states in section 126.96.36.199.1:
"If the Locks vector contains one and only one entry (NumberOfRequestedLocks ==
1) and TypeOfLock has the CANCEL_LOCK bit set, the client is requesting that the
server cancel a previously requested but unacknowledged lock."
My newly pushed smbtorture4 test, part of RAW-LOCK-ASYNC, shows a W2K8R2 server accepting a request with the CANCEL_LOCK bit set that contains multiple entries in the lock array, ie NumberOfRequestedLocks == 2. The server then seems to cancel the first outstanding lock and return SUCCESS.
More information about the cifs-protocol