Bug 6974 - a 0-byte read of a locked file range returns different error than Windows
a 0-byte read of a locked file range returns different error than Windows
Status: NEW
Product: Samba 4.0
Classification: Unclassified
Component: File services
unspecified
x64 Linux
: P3 minor
: ---
Assigned To: Andrew Tridgell
samba4-qa@samba.org
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-12-07 18:07 UTC by Steven Danneman
Modified: 2010-03-08 04:33 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steven Danneman 2009-12-07 18:07:43 UTC
This is another case where the Windows behavior may be incorrect.  It's also a
corner case scenario so isn't high priority for a fix.

When attempting a 0-byte read on a range of a file that is locked, Windows returns STATUS_OK to the read while Samba4 server returns STATUS_FILE_LOCK_CONFLICT.

This is exercised by the RAW-LOCK-ZEROBYTEREAD and SMB2-LOCK-ZEROBYTEREAD smbtorture4 tests.

These tests are currently listed in source4/selftest/knownfail
Comment 1 Matthias Dieter Wallnöfer 2010-03-08 04:33:23 UTC
Reassign file server related bugs up to tridge.