Bug 6958 - byte range lock requests greater than 64-bit do not return the proper error code
Summary: byte range lock requests greater than 64-bit do not return the proper error code
Status: NEW
Alias: None
Product: Samba 3.6
Classification: Unclassified
Component: File services (show other bugs)
Version: unspecified
Hardware: All Linux
: P3 normal
Target Milestone: ---
Assignee: Volker Lendecke
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-02 19:11 UTC by Steven Danneman
Modified: 2009-12-02 19:11 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steven Danneman 2009-12-02 19:11:38 UTC 
In versions of Windows < Win7 a request for a byte range lock who's offset plus
length was greater than 64-bits would return NT_STATUS_OK.  Win7 introduced the
new error code STATUS_INVALID_LOCK_RANGE.

smbd should check for range violations and now return this error.  
The RAW-LOCK-LOCKX, SMB2-LOCK-LOCK, and SMB2-LOCK-VALID-REQUEST tests
in smbtorture4 exercise this behavior.