summaryrefslogtreecommitdiff
path: root/source3/selftest
diff options
context:
space:
mode:
authorVolker Lendecke <vl@samba.org>2019-06-19 17:50:54 +0200
committerJeremy Allison <jra@samba.org>2019-06-20 17:18:18 +0000
commit3f6ed6e35239507ebe78091b9e1b4af7b644e3fd (patch)
tree01a358f65ab47abbb0839db80895acc89bf801cb /source3/selftest
parentb20231a1abb6d790dcb667f7010ec3b0b1ecb00b (diff)
downloadsamba-3f6ed6e35239507ebe78091b9e1b4af7b644e3fd.tar.gz
torture3: Run a blocking lock&x call with a subsequent read
Samba aborts the read&x after a blocked, but eventually successful locking&x call. Both Windows and source4/ntvfs do the read properly, source3/smbd does not. With later code, this will become possible much easier. Lets see if it's worth it given that we've got away with this forever. Signed-off-by: Volker Lendecke <vl@samba.org> Reviewed-by: Jeremy Allison <jra@samba.org>
Diffstat (limited to 'source3/selftest')
-rwxr-xr-xsource3/selftest/tests.py1
1 files changed, 1 insertions, 0 deletions
diff --git a/source3/selftest/tests.py b/source3/selftest/tests.py
index df30cb49cec..8e766d4fedc 100755
--- a/source3/selftest/tests.py
+++ b/source3/selftest/tests.py
@@ -81,6 +81,7 @@ plantestsuite("samba3.blackbox.registry.upgrade", "nt4_dc:local", [os.path.join(
tests = ["FDPASS", "LOCK1", "LOCK2", "LOCK3", "LOCK4", "LOCK5", "LOCK6", "LOCK7", "LOCK9",
"LOCK10",
"LOCK11",
+ "LOCK12",
"UNLINK", "BROWSE", "ATTR", "TRANS2", "TORTURE",
"OPLOCK1", "OPLOCK2", "OPLOCK4", "STREAMERROR",
"DIR", "DIR1", "DIR-CREATETIME", "TCON", "TCONDEV", "RW1", "RW2", "RW3", "LARGE_READX", "RW-SIGNING",