summaryrefslogtreecommitdiff
path: root/source4/selftest/knownfail
diff options
context:
space:
mode:
authorAndrew Tridgell <tridge@samba.org>2009-11-27 14:54:22 +1100
committerAndrew Tridgell <tridge@samba.org>2009-11-27 16:05:06 +1100
commitf6ecb4efb063617771dfa519911ae8af069c0f9a (patch)
tree34c58208e8244296245e735f43ccaccb683d2d94 /source4/selftest/knownfail
parent0920e0b63b806c8ed4839271048dd4924ed02b2b (diff)
downloadsamba-f6ecb4efb063617771dfa519911ae8af069c0f9a.tar.gz
samba-f6ecb4efb063617771dfa519911ae8af069c0f9a.tar.bz2
samba-f6ecb4efb063617771dfa519911ae8af069c0f9a.zip
s4-torture: fixed expected error codes for s4 in SMB2-LOCK
I think the error/success codes returned by windows for these tests are quite bogus. The ones s4 gives are much more reasonable. The locking ones returning NT_STATUS_SUCCESS could lead to data loss, as an application thinks it has a file locked correctly when it fact it doesn't, so it could do an unsafe modify.
Diffstat (limited to 'source4/selftest/knownfail')
-rw-r--r--source4/selftest/knownfail2
1 files changed, 2 insertions, 0 deletions
diff --git a/source4/selftest/knownfail b/source4/selftest/knownfail
index 3694aede1b..3528ff6865 100644
--- a/source4/selftest/knownfail
+++ b/source4/selftest/knownfail
@@ -64,3 +64,5 @@ samba4.ntvfs.cifs.base.maximum_allowed
samba4.base.createx_access # this test is broken for non-administrator users
samba4.smb2.oplock # oplocks in the s4 SMB2 server are a mess
samba4.smb2.lock.*.VALID-REQUEST # the s4 SMB2 server doesn't check lock ranges
+samba4.smb2.lock.*.CANCEL-TDIS # wrong error code
+samba4.smb2.lock.*.CANCEL-LOGOFF # wrong error code