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.