summaryrefslogtreecommitdiff
path: root/source3/torture/torture.c
diff options
context:
space:
mode:
authorVolker Lendecke <vl@samba.org>2012-01-05 17:44:44 +0100
committerVolker Lendecke <vlendec@samba.org>2012-01-05 20:29:59 +0100
commitf97216eb4ae1052e435d83ce51a7067fa6697ff4 (patch)
tree9f6d5d7740271aa00a4db4c32180d68be37a26d7 /source3/torture/torture.c
parent515dfe6c7ff9f6aed94a51960bb26aabb6fb449b (diff)
downloadsamba-f97216eb4ae1052e435d83ce51a7067fa6697ff4.tar.gz
samba-f97216eb4ae1052e435d83ce51a7067fa6697ff4.tar.bz2
samba-f97216eb4ae1052e435d83ce51a7067fa6697ff4.zip
s3: Add a test for proper brlock cleanup
We need to improve the server here. Maybe we should validate the brlock entry whenever we detect a read/write being blocked from locking? This is not our hot code path anyway, and it would gain us significant robustness. The code might become quite a bit simpler as well.
Diffstat (limited to 'source3/torture/torture.c')
-rw-r--r--source3/torture/torture.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/source3/torture/torture.c b/source3/torture/torture.c
index 9d18f72271..8535333a28 100644
--- a/source3/torture/torture.c
+++ b/source3/torture/torture.c
@@ -8880,6 +8880,7 @@ static struct {
{ "SMB2-MULTI-CHANNEL", run_smb2_multi_channel },
{ "SMB2-SESSION-REAUTH", run_smb2_session_reauth },
{ "CLEANUP1", run_cleanup1 },
+ { "CLEANUP2", run_cleanup2 },
{ "LOCAL-SUBSTITUTE", run_local_substitute, 0},
{ "LOCAL-GENCACHE", run_local_gencache, 0},
{ "LOCAL-TALLOC-DICT", run_local_talloc_dict, 0},