From f97216eb4ae1052e435d83ce51a7067fa6697ff4 Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Thu, 5 Jan 2012 17:44:44 +0100 Subject: 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. --- source3/torture/proto.h | 1 + 1 file changed, 1 insertion(+) (limited to 'source3/torture/proto.h') diff --git a/source3/torture/proto.h b/source3/torture/proto.h index 19e7a72a70..8d661aada9 100644 --- a/source3/torture/proto.h +++ b/source3/torture/proto.h @@ -102,5 +102,6 @@ bool run_smb2_session_reauth(int dummy); bool run_local_conv_auth_info(int dummy); bool run_local_sprintf_append(int dummy); bool run_cleanup1(int dummy); +bool run_cleanup2(int dummy); #endif /* __TORTURE_H__ */ -- cgit