summaryrefslogtreecommitdiff
path: root/source4/smb_server/smb2
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/smb_server/smb2
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/smb_server/smb2')
0 files changed, 0 insertions, 0 deletions