[cifs-protocol] [REG:112120410054506] FSCTL_SRV_COPYCHUNK locking discrepancies between Windows versions

[Edgar Olougouna]

David,
Can you please provide the network traces? 
I will research this and follow-up. 

Thanks,
Edgar

-----Original Message-----
From: Obaid Farooqi 
Sent: Tuesday, December 04, 2012 10:49 AM
To: David Disseldorp
Cc: cifs-protocol at cifs.org; pfif at tridgell.net; MSSolve Case Email
Subject: RE:[REG:112120410054506] FSCTL_SRV_COPYCHUNK locking discrepancies between Windows versions

Hi David:
Thanks for contacting Microsoft. A member of open specifications team will be in touch soon.

Regards,
Obaid Farooqi
Escalation Engineer | Microsoft

Exceeding your expectations is my highest priority.  If you would like to provide feedback on your case you may contact my manager at nkang at Microsoft dot com


-----Original Message-----
From: David Disseldorp [mailto:ddiss at suse.de]
Sent: Tuesday, December 04, 2012 4:42 AM
To: Interoperability Documentation Help; cifs-protocol at cifs.org; pfif at tridgell.net
Subject: FSCTL_SRV_COPYCHUNK locking discrepancies between Windows versions

Hi DocHelp,

Windows server behaviour when processing SMB2 FSCTL_SRV_COPYCHUNK requests under byte-range lock conditions varies between versions.
These discrepancies do not appear to be documented.

Under Windows Server 2012, an SMB2 FSCTL_SRV_COPYCHUNK request with a SourceKey, SourceOffset and Length referring to a locked file range (SMB2_LOCKFLAG_EXCLUSIVE), fails with STATUS_FILE_LOCK_CONFLICT.

Under Windows 7 and Windows Server 2008r2, this is not the case. An FSCTL_SRV_COPYCHUNK request with a SourceKey, SourceOffset and Length referring to a locked file range succeeds.

An FSCTL_SRV_COPYCHUNK request with a _target_ FileID, TargetOffset and Length referring to a locked file range fails on all tested platforms (Windows Server 2012, Windows Server 2008r2 and Windows 7) with STATUS_FILE_LOCK_CONFLICT.

Network traces available.

Regards, David
Microsoft is committed to protecting your privacy.  Please read the Microsoft Privacy Statement for more information.The above is an email for a support case from Microsoft Corp.REPLY ALL TO THIS MESSAGE or INCLUDE casemail at microsoft.com IN YOUR REPLY if you want your response added to the case automatically. For technical assistance, please include the Support Engineer on the TO: line. Thank you.