s4-torture: fixed expected error codes for s4 in SMB2-LOCK
authorAndrew Tridgell <tridge@samba.org>
Fri, 27 Nov 2009 03:54:22 +0000 (14:54 +1100)
committerAndrew Tridgell <tridge@samba.org>
Fri, 27 Nov 2009 05:05:06 +0000 (16:05 +1100)
commitf6ecb4efb063617771dfa519911ae8af069c0f9a
tree34c58208e8244296245e735f43ccaccb683d2d94
parent0920e0b63b806c8ed4839271048dd4924ed02b2b
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.
source4/selftest/knownfail
source4/torture/smb2/lock.c