sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-20 14:03:59 +03:00
Code
samba-mirror/source4/torture/basic/locking.c

816 lines
30 KiB
C
Raw Normal View History

r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
/*
Unix SMB/CIFS implementation.
basic locking tests
Copyright (C) Andrew Tridgell 2000-2004
Copyright (C) Jeremy Allison 2000-2004
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
r23792: convert Samba4 to GPLv3 There are still a few tidyups of old FSF addresses to come (in both s3 and s4). More commits soon. (This used to be commit fcf38a38ac691abd0fa51b89dc951a08e89fdafa)
2007-07-10 02:07:03 +00:00
the Free Software Foundation; either version 3 of the License, or
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
r23792: convert Samba4 to GPLv3 There are still a few tidyups of old FSF addresses to come (in both s3 and s4). More commits soon. (This used to be commit fcf38a38ac691abd0fa51b89dc951a08e89fdafa)
2007-07-10 02:07:03 +00:00
along with this program. If not, see <http://www.gnu.org/licenses/>.
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
*/
#include "includes.h"
r12694: Move some headers to the directory of the subsystem they belong to. (This used to be commit c722f665c90103f3ed57621c460e32ad33e7a8a3)
2006-01-03 15:40:05 +00:00
#include "libcli/libcli.h"
r14527: Fix build problems. (This used to be commit 863ca4014d9b821706ee90f58ab5d5cf3899a4c7)
2006-03-17 17:59:58 +00:00
#include "torture/util.h"
r3447: more include/system/XXX.h include files (This used to be commit 264ce9181089922547e8f6f67116f2d7277a5105)
2004-11-02 00:24:21 +00:00
#include "system/time.h"
r5298: - got rid of pstring.h from includes.h. This at least makes it a bit less likely that anyone will use pstring for new code - got rid of winbind_client.h from includes.h. This one triggered a huge change, as winbind_client.h was including system/filesys.h and defining the old uint32 and uint16 types, as well as its own pstring and fstring. (This used to be commit 9db6c79e902ec538108d6b7d3324039aabe1704f)
2005-02-10 05:09:35 +00:00
#include "system/filesys.h"
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
#define BASEDIR "\\locktest"
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
/*
This test checks for two things:
1) correct support for retaining locks over a close (ie. the server
must not use posix semantics)
2) support for lock timeouts
*/
r23810: Make things static, and remove unsued code. This includes some of the original ildap ldap client API. ldb provides a much easier abstraction on this to use, and doesn't use these functions. Andrew Bartlett (This used to be commit dc27a7e41c297472675e8c251bb14327a1af3902)
2007-07-10 11:37:30 +00:00
static bool torture_locktest1(struct torture_context *tctx,
struct smbcli_state *cli1,
struct smbcli_state *cli2)
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
{
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
const char *fname = BASEDIR "\\lockt1.lck";
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
int fnum1, fnum2, fnum3;
time_t t1, t2;
uint_t lock_timeout;
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
if (!torture_setup_dir(cli1, BASEDIR)) {
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
return false;
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
}
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
fnum1 = smbcli_open(cli1->tree, fname, O_RDWR|O_CREAT|O_EXCL, DENY_NONE);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx, fnum1 != -1,
talloc_asprintf(tctx,
"open of %s failed (%s)\n", fname, smbcli_errstr(cli1->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
fnum2 = smbcli_open(cli1->tree, fname, O_RDWR, DENY_NONE);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx, fnum2 != -1, talloc_asprintf(tctx,
"open2 of %s failed (%s)\n", fname, smbcli_errstr(cli1->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
fnum3 = smbcli_open(cli2->tree, fname, O_RDWR, DENY_NONE);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx, fnum3 != -1, talloc_asprintf(tctx,
"open3 of %s failed (%s)\n", fname, smbcli_errstr(cli2->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx,
smbcli_lock(cli1->tree, fnum1, 0, 4, 0, WRITE_LOCK),
talloc_asprintf(tctx, "lock1 failed (%s)", smbcli_errstr(cli1->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_lock(cli2->tree, fnum3, 0, 4, 0, WRITE_LOCK)),
"lock2 succeeded! This is a locking bug\n");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
if (!check_error(__location__, cli2, ERRDOS, ERRlock,
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
NT_STATUS_LOCK_NOT_GRANTED)) return false;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_lock(cli2->tree, fnum3, 0, 4, 0, WRITE_LOCK)),
"lock2 succeeded! This is a locking bug\n");
if (!check_error(__location__, cli2, ERRDOS, ERRlock,
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
NT_STATUS_FILE_LOCK_CONFLICT)) return false;
r3029: implemented byte range lock timeouts. This adds a pvfs_wait_message() routine which uses the new messaging system, event timers and talloc destructors to give a nice generic async event handling system with a easy to use interface. The extensions to pvfs_lock.c are based on calls to pvfs_wait_message() routines. We now pass all of our smbtorture locking tests, although while writing this code I have thought of some additonal tests that should be added, particularly for lock cancel operations. I'll work on that soon. This commit also extends the smbtorture lock tests to test the rather weird 0xEEFFFFFF locking semantics that I have discovered in win2003. Win2003 treats the 0xEEFFFFFF boundary as special, and will give different error codes on either side of it. Locks on both sides are allowed, the only difference is which error code is given when a lock is denied. Anyone like to hazard a guess as to why? It has me stumped. (This used to be commit 4395c0557ab175d6a8dd99df03c266325949ffa5)
2004-10-18 07:40:17 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx,
smbcli_lock(cli1->tree, fnum1, 5, 9, 0, WRITE_LOCK),
talloc_asprintf(tctx,
"lock1 failed (%s)", smbcli_errstr(cli1->tree)));
r3029: implemented byte range lock timeouts. This adds a pvfs_wait_message() routine which uses the new messaging system, event timers and talloc destructors to give a nice generic async event handling system with a easy to use interface. The extensions to pvfs_lock.c are based on calls to pvfs_wait_message() routines. We now pass all of our smbtorture locking tests, although while writing this code I have thought of some additonal tests that should be added, particularly for lock cancel operations. I'll work on that soon. This commit also extends the smbtorture lock tests to test the rather weird 0xEEFFFFFF locking semantics that I have discovered in win2003. Win2003 treats the 0xEEFFFFFF boundary as special, and will give different error codes on either side of it. Locks on both sides are allowed, the only difference is which error code is given when a lock is denied. Anyone like to hazard a guess as to why? It has me stumped. (This used to be commit 4395c0557ab175d6a8dd99df03c266325949ffa5)
2004-10-18 07:40:17 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_lock(cli2->tree, fnum3, 5, 9, 0, WRITE_LOCK)),
"lock2 succeeded! This is a locking bug");
if (!check_error(__location__, cli2, ERRDOS, ERRlock,
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
NT_STATUS_LOCK_NOT_GRANTED)) return false;
r3029: implemented byte range lock timeouts. This adds a pvfs_wait_message() routine which uses the new messaging system, event timers and talloc destructors to give a nice generic async event handling system with a easy to use interface. The extensions to pvfs_lock.c are based on calls to pvfs_wait_message() routines. We now pass all of our smbtorture locking tests, although while writing this code I have thought of some additonal tests that should be added, particularly for lock cancel operations. I'll work on that soon. This commit also extends the smbtorture lock tests to test the rather weird 0xEEFFFFFF locking semantics that I have discovered in win2003. Win2003 treats the 0xEEFFFFFF boundary as special, and will give different error codes on either side of it. Locks on both sides are allowed, the only difference is which error code is given when a lock is denied. Anyone like to hazard a guess as to why? It has me stumped. (This used to be commit 4395c0557ab175d6a8dd99df03c266325949ffa5)
2004-10-18 07:40:17 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_lock(cli2->tree, fnum3, 0, 4, 0, WRITE_LOCK)),
"lock2 succeeded! This is a locking bug");
if (!check_error(__location__, cli2, ERRDOS, ERRlock,
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
NT_STATUS_LOCK_NOT_GRANTED)) return false;
r3029: implemented byte range lock timeouts. This adds a pvfs_wait_message() routine which uses the new messaging system, event timers and talloc destructors to give a nice generic async event handling system with a easy to use interface. The extensions to pvfs_lock.c are based on calls to pvfs_wait_message() routines. We now pass all of our smbtorture locking tests, although while writing this code I have thought of some additonal tests that should be added, particularly for lock cancel operations. I'll work on that soon. This commit also extends the smbtorture lock tests to test the rather weird 0xEEFFFFFF locking semantics that I have discovered in win2003. Win2003 treats the 0xEEFFFFFF boundary as special, and will give different error codes on either side of it. Locks on both sides are allowed, the only difference is which error code is given when a lock is denied. Anyone like to hazard a guess as to why? It has me stumped. (This used to be commit 4395c0557ab175d6a8dd99df03c266325949ffa5)
2004-10-18 07:40:17 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_lock(cli2->tree, fnum3, 0, 4, 0, WRITE_LOCK)),
"lock2 succeeded! This is a locking bug");
if (!check_error(__location__, cli2, ERRDOS, ERRlock,
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
NT_STATUS_FILE_LOCK_CONFLICT)) return false;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
lock_timeout = (6 + (random() % 20));
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "Testing lock timeout with timeout=%u\n",
lock_timeout);
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
t1 = time(NULL);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_lock(cli2->tree, fnum3, 0, 4, lock_timeout * 1000, WRITE_LOCK)),
"lock3 succeeded! This is a locking bug\n");
if (!check_error(__location__, cli2, ERRDOS, ERRlock,
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
NT_STATUS_FILE_LOCK_CONFLICT)) return false;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
t2 = time(NULL);
if (t2 - t1 < 5) {
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_fail(tctx,
"error: This server appears not to support timed lock requests");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
}
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "server slept for %u seconds for a %u second timeout\n",
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
(uint_t)(t2-t1), lock_timeout);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx, smbcli_close(cli1->tree, fnum2),
talloc_asprintf(tctx, "close1 failed (%s)", smbcli_errstr(cli1->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_lock(cli2->tree, fnum3, 0, 4, 0, WRITE_LOCK)),
"lock4 succeeded! This is a locking bug");
if (!check_error(__location__, cli2, ERRDOS, ERRlock,
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
NT_STATUS_FILE_LOCK_CONFLICT)) return false;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx, smbcli_close(cli1->tree, fnum1),
talloc_asprintf(tctx, "close2 failed (%s)", smbcli_errstr(cli1->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx, smbcli_close(cli2->tree, fnum3),
talloc_asprintf(tctx, "close3 failed (%s)", smbcli_errstr(cli2->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx, smbcli_unlink(cli1->tree, fname),
talloc_asprintf(tctx, "unlink failed (%s)", smbcli_errstr(cli1->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
return true;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
}
/*
This test checks that
1) the server supports multiple locking contexts on the one SMB
connection, distinguished by PID.
2) the server correctly fails overlapping locks made by the same PID (this
goes against POSIX behaviour, which is why it is tricky to implement)
3) the server denies unlock requests by an incorrect client PID
*/
r23810: Make things static, and remove unsued code. This includes some of the original ildap ldap client API. ldb provides a much easier abstraction on this to use, and doesn't use these functions. Andrew Bartlett (This used to be commit dc27a7e41c297472675e8c251bb14327a1af3902)
2007-07-10 11:37:30 +00:00
static bool torture_locktest2(struct torture_context *tctx,
struct smbcli_state *cli)
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
{
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
const char *fname = BASEDIR "\\lockt2.lck";
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
int fnum1, fnum2, fnum3;
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
if (!torture_setup_dir(cli, BASEDIR)) {
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
return false;
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
}
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "Testing pid context\n");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
cli->session->pid = 1;
fnum1 = smbcli_open(cli->tree, fname, O_RDWR|O_CREAT|O_EXCL, DENY_NONE);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx, fnum1 != -1,
talloc_asprintf(tctx,
"open of %s failed (%s)", fname, smbcli_errstr(cli->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
fnum2 = smbcli_open(cli->tree, fname, O_RDWR, DENY_NONE);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx, fnum2 != -1,
talloc_asprintf(tctx, "open2 of %s failed (%s)",
fname, smbcli_errstr(cli->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
cli->session->pid = 2;
fnum3 = smbcli_open(cli->tree, fname, O_RDWR, DENY_NONE);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx, fnum3 != -1,
talloc_asprintf(tctx,
"open3 of %s failed (%s)\n", fname, smbcli_errstr(cli->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
cli->session->pid = 1;
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx,
smbcli_lock(cli->tree, fnum1, 0, 4, 0, WRITE_LOCK),
talloc_asprintf(tctx,
"lock1 failed (%s)", smbcli_errstr(cli->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_lock(cli->tree, fnum1, 0, 4, 0, WRITE_LOCK)),
"WRITE lock1 succeeded! This is a locking bug");
if (!check_error(__location__, cli, ERRDOS, ERRlock,
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
NT_STATUS_LOCK_NOT_GRANTED)) return false;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_lock(cli->tree, fnum2, 0, 4, 0, WRITE_LOCK)),
"WRITE lock2 succeeded! This is a locking bug");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
if (!check_error(__location__, cli, ERRDOS, ERRlock,
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
NT_STATUS_LOCK_NOT_GRANTED)) return false;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_lock(cli->tree, fnum2, 0, 4, 0, READ_LOCK)),
"READ lock2 succeeded! This is a locking bug");
if (!check_error(__location__, cli, ERRDOS, ERRlock,
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
NT_STATUS_FILE_LOCK_CONFLICT)) return false;
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx,
smbcli_lock(cli->tree, fnum1, 100, 4, 0, WRITE_LOCK),
talloc_asprintf(tctx,
"lock at 100 failed (%s)", smbcli_errstr(cli->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
cli->session->pid = 2;
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_unlock(cli->tree, fnum1, 100, 4)),
"unlock at 100 succeeded! This is a locking bug");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_unlock(cli->tree, fnum1, 0, 4)),
"unlock1 succeeded! This is a locking bug");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
if (!check_error(__location__, cli,
r8117: fixed a bunch more dos error code handing. The biggest change was fixing the RAW-CONTEXT test. It was forcing capabilities to zero in an attempt to not negotiated extended security, but as a side effect it was forcing negotiation of dos error codes. This confused the hell out of the test code! Also fixed a bunch of places incorrectly using NT_STATUS_V() instead of NT_STATUS_EQUAL() and several places that had the wrong dos status codes (This used to be commit 0b22744f40804a0d6dc94bfc40ec09306f584f7e)
2005-07-04 05:05:28 +00:00
ERRDOS, ERRnotlocked,
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
NT_STATUS_RANGE_NOT_LOCKED)) return false;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_unlock(cli->tree, fnum1, 0, 8)),
"unlock2 succeeded! This is a locking bug");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
if (!check_error(__location__, cli,
ERRDOS, ERRnotlocked,
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
NT_STATUS_RANGE_NOT_LOCKED)) return false;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_lock(cli->tree, fnum3, 0, 4, 0, WRITE_LOCK)),
"lock3 succeeded! This is a locking bug");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
if (!check_error(__location__, cli, ERRDOS, ERRlock, NT_STATUS_LOCK_NOT_GRANTED)) return false;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
cli->session->pid = 1;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx, smbcli_close(cli->tree, fnum1),
talloc_asprintf(tctx, "close1 failed (%s)", smbcli_errstr(cli->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx, smbcli_close(cli->tree, fnum2),
talloc_asprintf(tctx, "close2 failed (%s)", smbcli_errstr(cli->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx, smbcli_close(cli->tree, fnum3),
talloc_asprintf(tctx, "close3 failed (%s)", smbcli_errstr(cli->tree)));
return true;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
}
/*
This test checks that
1) the server supports the full offset range in lock requests
*/
r23810: Make things static, and remove unsued code. This includes some of the original ildap ldap client API. ldb provides a much easier abstraction on this to use, and doesn't use these functions. Andrew Bartlett (This used to be commit dc27a7e41c297472675e8c251bb14327a1af3902)
2007-07-10 11:37:30 +00:00
static bool torture_locktest3(struct torture_context *tctx,
struct smbcli_state *cli1,
struct smbcli_state *cli2)
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
{
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
const char *fname = BASEDIR "\\lockt3.lck";
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
int fnum1, fnum2, i;
uint32_t offset;
extern int torture_numops;
#define NEXT_OFFSET offset += (~(uint32_t)0) / torture_numops
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "Testing 32 bit offset ranges");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
if (!torture_setup_dir(cli1, BASEDIR)) {
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
return false;
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
}
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
fnum1 = smbcli_open(cli1->tree, fname, O_RDWR|O_CREAT|O_EXCL, DENY_NONE);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx, fnum1 != -1,
talloc_asprintf(tctx, "open of %s failed (%s)\n", fname, smbcli_errstr(cli1->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
fnum2 = smbcli_open(cli2->tree, fname, O_RDWR, DENY_NONE);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx, fnum2 != -1,
talloc_asprintf(tctx, "open2 of %s failed (%s)\n", fname, smbcli_errstr(cli2->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "Establishing %d locks\n", torture_numops);
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
for (offset=i=0;i<torture_numops;i++) {
NEXT_OFFSET;
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx,
smbcli_lock(cli1->tree, fnum1, offset-1, 1, 0, WRITE_LOCK),
talloc_asprintf(tctx, "lock1 %d failed (%s)", i, smbcli_errstr(cli1->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx,
smbcli_lock(cli2->tree, fnum2, offset-2, 1, 0, WRITE_LOCK),
talloc_asprintf(tctx, "lock2 %d failed (%s)",
i, smbcli_errstr(cli1->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
}
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "Testing %d locks\n", torture_numops);
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
for (offset=i=0;i<torture_numops;i++) {
NEXT_OFFSET;
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, offset-2, 1, 0, WRITE_LOCK)),
talloc_asprintf(tctx, "error: lock1 %d succeeded!", i));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_lock(cli2->tree, fnum2, offset-1, 1, 0, WRITE_LOCK)),
talloc_asprintf(tctx, "error: lock2 %d succeeded!", i));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, offset-1, 1, 0, WRITE_LOCK)),
talloc_asprintf(tctx, "error: lock3 %d succeeded!", i));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx,
!NT_STATUS_IS_OK(smbcli_lock(cli2->tree, fnum2, offset-2, 1, 0, WRITE_LOCK)),
talloc_asprintf(tctx, "error: lock4 %d succeeded!", i));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
}
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "Removing %d locks\n", torture_numops);
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
for (offset=i=0;i<torture_numops;i++) {
NEXT_OFFSET;
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx,
smbcli_unlock(cli1->tree, fnum1, offset-1, 1),
talloc_asprintf(tctx, "unlock1 %d failed (%s)",
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
i,
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
smbcli_errstr(cli1->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx,
smbcli_unlock(cli2->tree, fnum2, offset-2, 1),
talloc_asprintf(tctx, "unlock2 %d failed (%s)",
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
i,
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
smbcli_errstr(cli1->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
}
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx, smbcli_close(cli1->tree, fnum1),
talloc_asprintf(tctx, "close1 failed (%s)", smbcli_errstr(cli1->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx, smbcli_close(cli2->tree, fnum2),
talloc_asprintf(tctx, "close2 failed (%s)", smbcli_errstr(cli2->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx, smbcli_unlink(cli1->tree, fname),
talloc_asprintf(tctx, "unlink failed (%s)", smbcli_errstr(cli1->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
return true;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
}
#define EXPECTED(ret, v) if ((ret) != (v)) { \
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
torture_comment(tctx, "** "); correct = false; \
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
}
/*
looks at overlapping locks
*/
r23810: Make things static, and remove unsued code. This includes some of the original ildap ldap client API. ldb provides a much easier abstraction on this to use, and doesn't use these functions. Andrew Bartlett (This used to be commit dc27a7e41c297472675e8c251bb14327a1af3902)
2007-07-10 11:37:30 +00:00
static bool torture_locktest4(struct torture_context *tctx,
struct smbcli_state *cli1,
struct smbcli_state *cli2)
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
{
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
const char *fname = BASEDIR "\\lockt4.lck";
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
int fnum1, fnum2, f;
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
bool ret;
r4063: - change char * -> uint8_t in struct request_buffer - change smbcli_read/write to take void * for the buffers to match read(2)/write(2) all this fixes a lot of gcc-4 warnings metze (This used to be commit b94f92bc6637f748d6f7049f4f9a30b0b8d18a7a)
2004-12-04 13:56:25 +00:00
uint8_t buf[1000];
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
bool correct = true;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
if (!torture_setup_dir(cli1, BASEDIR)) {
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
return false;
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
}
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
fnum1 = smbcli_open(cli1->tree, fname, O_RDWR|O_CREAT|O_EXCL, DENY_NONE);
fnum2 = smbcli_open(cli2->tree, fname, O_RDWR, DENY_NONE);
memset(buf, 0, sizeof(buf));
if (smbcli_write(cli1->tree, fnum1, 0, buf, 0, sizeof(buf)) != sizeof(buf)) {
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "Failed to create file\n");
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
correct = false;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
goto fail;
}
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 0, 4, 0, WRITE_LOCK)) &&
NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 2, 4, 0, WRITE_LOCK));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, false);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "the same process %s set overlapping write locks\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 10, 4, 0, READ_LOCK)) &&
NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 12, 4, 0, READ_LOCK));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "the same process %s set overlapping read locks\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 20, 4, 0, WRITE_LOCK)) &&
NT_STATUS_IS_OK(smbcli_lock(cli2->tree, fnum2, 22, 4, 0, WRITE_LOCK));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, false);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "a different connection %s set overlapping write locks\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 30, 4, 0, READ_LOCK)) &&
NT_STATUS_IS_OK(smbcli_lock(cli2->tree, fnum2, 32, 4, 0, READ_LOCK));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "a different connection %s set overlapping read locks\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK((cli1->session->pid = 1, smbcli_lock(cli1->tree, fnum1, 40, 4, 0, WRITE_LOCK))) &&
NT_STATUS_IS_OK((cli1->session->pid = 2, smbcli_lock(cli1->tree, fnum1, 42, 4, 0, WRITE_LOCK)));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, false);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "a different pid %s set overlapping write locks\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK((cli1->session->pid = 1, smbcli_lock(cli1->tree, fnum1, 50, 4, 0, READ_LOCK))) &&
NT_STATUS_IS_OK((cli1->session->pid = 2, smbcli_lock(cli1->tree, fnum1, 52, 4, 0, READ_LOCK)));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "a different pid %s set overlapping read locks\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 60, 4, 0, READ_LOCK)) &&
NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 60, 4, 0, READ_LOCK));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "the same process %s set the same read lock twice\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 70, 4, 0, WRITE_LOCK)) &&
NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 70, 4, 0, WRITE_LOCK));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, false);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "the same process %s set the same write lock twice\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 80, 4, 0, READ_LOCK)) &&
NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 80, 4, 0, WRITE_LOCK));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, false);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "the same process %s overlay a read lock with a write lock\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 90, 4, 0, WRITE_LOCK)) &&
NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 90, 4, 0, READ_LOCK));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "the same process %s overlay a write lock with a read lock\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK((cli1->session->pid = 1, smbcli_lock(cli1->tree, fnum1, 100, 4, 0, WRITE_LOCK))) &&
NT_STATUS_IS_OK((cli1->session->pid = 2, smbcli_lock(cli1->tree, fnum1, 100, 4, 0, READ_LOCK)));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, false);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "a different pid %s overlay a write lock with a read lock\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 110, 4, 0, READ_LOCK)) &&
NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 112, 4, 0, READ_LOCK)) &&
NT_STATUS_IS_OK(smbcli_unlock(cli1->tree, fnum1, 110, 6));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, false);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "the same process %s coalesce read locks\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 120, 4, 0, WRITE_LOCK)) &&
(smbcli_read(cli2->tree, fnum2, buf, 120, 4) == 4);
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, false);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "this server %s strict write locking\n", ret?"doesn't do":"does");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 130, 4, 0, READ_LOCK)) &&
(smbcli_write(cli2->tree, fnum2, 0, buf, 130, 4) == 4);
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, false);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "this server %s strict read locking\n", ret?"doesn't do":"does");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 140, 4, 0, READ_LOCK)) &&
NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 140, 4, 0, READ_LOCK)) &&
NT_STATUS_IS_OK(smbcli_unlock(cli1->tree, fnum1, 140, 4)) &&
NT_STATUS_IS_OK(smbcli_unlock(cli1->tree, fnum1, 140, 4));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "this server %s do recursive read locking\n", ret?"does":"doesn't");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 150, 4, 0, WRITE_LOCK)) &&
NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 150, 4, 0, READ_LOCK)) &&
NT_STATUS_IS_OK(smbcli_unlock(cli1->tree, fnum1, 150, 4)) &&
(smbcli_read(cli2->tree, fnum2, buf, 150, 4) == 4) &&
!(smbcli_write(cli2->tree, fnum2, 0, buf, 150, 4) == 4) &&
NT_STATUS_IS_OK(smbcli_unlock(cli1->tree, fnum1, 150, 4));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "this server %s do recursive lock overlays\n", ret?"does":"doesn't");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 160, 4, 0, READ_LOCK)) &&
NT_STATUS_IS_OK(smbcli_unlock(cli1->tree, fnum1, 160, 4)) &&
(smbcli_write(cli2->tree, fnum2, 0, buf, 160, 4) == 4) &&
(smbcli_read(cli2->tree, fnum2, buf, 160, 4) == 4);
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "the same process %s remove a read lock using write locking\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 170, 4, 0, WRITE_LOCK)) &&
NT_STATUS_IS_OK(smbcli_unlock(cli1->tree, fnum1, 170, 4)) &&
(smbcli_write(cli2->tree, fnum2, 0, buf, 170, 4) == 4) &&
(smbcli_read(cli2->tree, fnum2, buf, 170, 4) == 4);
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "the same process %s remove a write lock using read locking\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 190, 4, 0, WRITE_LOCK)) &&
NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 190, 4, 0, READ_LOCK)) &&
NT_STATUS_IS_OK(smbcli_unlock(cli1->tree, fnum1, 190, 4)) &&
!(smbcli_write(cli2->tree, fnum2, 0, buf, 190, 4) == 4) &&
(smbcli_read(cli2->tree, fnum2, buf, 190, 4) == 4);
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "the same process %s remove the first lock first\n", ret?"does":"doesn't");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
smbcli_close(cli1->tree, fnum1);
smbcli_close(cli2->tree, fnum2);
fnum1 = smbcli_open(cli1->tree, fname, O_RDWR, DENY_NONE);
f = smbcli_open(cli1->tree, fname, O_RDWR, DENY_NONE);
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 0, 8, 0, READ_LOCK)) &&
NT_STATUS_IS_OK(smbcli_lock(cli1->tree, f, 0, 1, 0, READ_LOCK)) &&
NT_STATUS_IS_OK(smbcli_close(cli1->tree, fnum1)) &&
((fnum1 = smbcli_open(cli1->tree, fname, O_RDWR, DENY_NONE)) != -1) &&
NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 7, 1, 0, WRITE_LOCK));
smbcli_close(cli1->tree, f);
smbcli_close(cli1->tree, fnum1);
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "the server %s have the NT byte range lock bug\n", !ret?"does":"doesn't");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
fail:
smbcli_close(cli1->tree, fnum1);
smbcli_close(cli2->tree, fnum2);
smbcli_unlink(cli1->tree, fname);
return correct;
}
/*
looks at lock upgrade/downgrade.
*/
r23810: Make things static, and remove unsued code. This includes some of the original ildap ldap client API. ldb provides a much easier abstraction on this to use, and doesn't use these functions. Andrew Bartlett (This used to be commit dc27a7e41c297472675e8c251bb14327a1af3902)
2007-07-10 11:37:30 +00:00
static bool torture_locktest5(struct torture_context *tctx, struct smbcli_state *cli1,
struct smbcli_state *cli2)
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
{
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
const char *fname = BASEDIR "\\lockt5.lck";
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
int fnum1, fnum2, fnum3;
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
bool ret;
r4063: - change char * -> uint8_t in struct request_buffer - change smbcli_read/write to take void * for the buffers to match read(2)/write(2) all this fixes a lot of gcc-4 warnings metze (This used to be commit b94f92bc6637f748d6f7049f4f9a30b0b8d18a7a)
2004-12-04 13:56:25 +00:00
uint8_t buf[1000];
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
bool correct = true;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
if (!torture_setup_dir(cli1, BASEDIR)) {
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
return false;
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
}
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
fnum1 = smbcli_open(cli1->tree, fname, O_RDWR|O_CREAT|O_EXCL, DENY_NONE);
fnum2 = smbcli_open(cli2->tree, fname, O_RDWR, DENY_NONE);
fnum3 = smbcli_open(cli1->tree, fname, O_RDWR, DENY_NONE);
memset(buf, 0, sizeof(buf));
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx, smbcli_write(cli1->tree, fnum1, 0, buf, 0, sizeof(buf)) == sizeof(buf),
"Failed to create file");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
/* Check for NT bug... */
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 0, 8, 0, READ_LOCK)) &&
NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum3, 0, 1, 0, READ_LOCK));
smbcli_close(cli1->tree, fnum1);
fnum1 = smbcli_open(cli1->tree, fname, O_RDWR, DENY_NONE);
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 7, 1, 0, WRITE_LOCK));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "this server %s the NT locking bug\n", ret ? "doesn't have" : "has");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
smbcli_close(cli1->tree, fnum1);
fnum1 = smbcli_open(cli1->tree, fname, O_RDWR, DENY_NONE);
smbcli_unlock(cli1->tree, fnum3, 0, 1);
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 0, 4, 0, WRITE_LOCK)) &&
NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 1, 1, 0, READ_LOCK));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "the same process %s overlay a write with a read lock\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
ret = NT_STATUS_IS_OK(smbcli_lock(cli2->tree, fnum2, 0, 4, 0, READ_LOCK));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, false);
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "a different processs %s get a read lock on the first process lock stack\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
/* Unlock the process 2 lock. */
smbcli_unlock(cli2->tree, fnum2, 0, 4);
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum3, 0, 4, 0, READ_LOCK));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, false);
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "the same processs on a different fnum %s get a read lock\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
/* Unlock the process 1 fnum3 lock. */
smbcli_unlock(cli1->tree, fnum3, 0, 4);
/* Stack 2 more locks here. */
ret = NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 0, 4, 0, READ_LOCK)) &&
NT_STATUS_IS_OK(smbcli_lock(cli1->tree, fnum1, 0, 4, 0, READ_LOCK));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "the same process %s stack read locks\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
/* Unlock the first process lock, then check this was the WRITE lock that was
removed. */
ret = NT_STATUS_IS_OK(smbcli_unlock(cli1->tree, fnum1, 0, 4)) &&
NT_STATUS_IS_OK(smbcli_lock(cli2->tree, fnum2, 0, 4, 0, READ_LOCK));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "the first unlock removes the %s lock\n", ret?"WRITE":"READ");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
/* Unlock the process 2 lock. */
smbcli_unlock(cli2->tree, fnum2, 0, 4);
/* We should have 3 stacked locks here. Ensure we need to do 3 unlocks. */
ret = NT_STATUS_IS_OK(smbcli_unlock(cli1->tree, fnum1, 1, 1)) &&
NT_STATUS_IS_OK(smbcli_unlock(cli1->tree, fnum1, 0, 4)) &&
NT_STATUS_IS_OK(smbcli_unlock(cli1->tree, fnum1, 0, 4));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
s4 torture: Two minor fixes to smbtorture BRL tests.
2009-02-09 21:59:40 -08:00
torture_comment(tctx, "the same process %s unlock the stack of 3 locks\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
/* Ensure the next unlock fails. */
ret = NT_STATUS_IS_OK(smbcli_unlock(cli1->tree, fnum1, 0, 4));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, false);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "the same process %s count the lock stack\n", !ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
/* Ensure connection 2 can get a write lock. */
ret = NT_STATUS_IS_OK(smbcli_lock(cli2->tree, fnum2, 0, 4, 0, WRITE_LOCK));
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
EXPECTED(ret, true);
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "a different processs %s get a write lock on the unlocked stack\n", ret?"can":"cannot");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
BASE-LOCK: fix LOCK5 We need to close all 3 file handle to make the unlink work. metze
2008-12-18 07:49:41 +01:00
torture_assert_ntstatus_ok(tctx, smbcli_close(cli1->tree, fnum1),
talloc_asprintf(tctx, "close1 failed (%s)", smbcli_errstr(cli1->tree)));
torture_assert_ntstatus_ok(tctx, smbcli_close(cli2->tree, fnum2),
talloc_asprintf(tctx, "close2 failed (%s)", smbcli_errstr(cli2->tree)));
torture_assert_ntstatus_ok(tctx, smbcli_close(cli1->tree, fnum3),
talloc_asprintf(tctx, "close2 failed (%s)", smbcli_errstr(cli2->tree)));
torture_assert_ntstatus_ok(tctx, smbcli_unlink(cli1->tree, fname),
talloc_asprintf(tctx, "unlink failed (%s)", smbcli_errstr(cli1->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
return correct;
}
/*
tries the unusual lockingX locktype bits
*/
r23810: Make things static, and remove unsued code. This includes some of the original ildap ldap client API. ldb provides a much easier abstraction on this to use, and doesn't use these functions. Andrew Bartlett (This used to be commit dc27a7e41c297472675e8c251bb14327a1af3902)
2007-07-10 11:37:30 +00:00
static bool torture_locktest6(struct torture_context *tctx,
struct smbcli_state *cli)
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
{
const char *fname[1] = { "\\lock6.txt" };
int i;
int fnum;
NTSTATUS status;
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
if (!torture_setup_dir(cli, BASEDIR)) {
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
return false;
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
}
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
for (i=0;i<1;i++) {
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "Testing %s\n", fname[i]);
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
smbcli_unlink(cli->tree, fname[i]);
fnum = smbcli_open(cli->tree, fname[i], O_RDWR|O_CREAT|O_EXCL, DENY_NONE);
status = smbcli_locktype(cli->tree, fnum, 0, 8, 0, LOCKING_ANDX_CHANGE_LOCKTYPE);
smbcli_close(cli->tree, fnum);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "CHANGE_LOCKTYPE gave %s\n", nt_errstr(status));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
fnum = smbcli_open(cli->tree, fname[i], O_RDWR, DENY_NONE);
status = smbcli_locktype(cli->tree, fnum, 0, 8, 0, LOCKING_ANDX_CANCEL_LOCK);
smbcli_close(cli->tree, fnum);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "CANCEL_LOCK gave %s\n", nt_errstr(status));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
smbcli_unlink(cli->tree, fname[i]);
}
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
return true;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
}
r23810: Make things static, and remove unsued code. This includes some of the original ildap ldap client API. ldb provides a much easier abstraction on this to use, and doesn't use these functions. Andrew Bartlett (This used to be commit dc27a7e41c297472675e8c251bb14327a1af3902)
2007-07-10 11:37:30 +00:00
static bool torture_locktest7(struct torture_context *tctx,
struct smbcli_state *cli1)
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
{
r4430: - fixed the BASE-LOCK* tests to use a subdirectory, and properly setup the directory before each test, thus avoiding errors due to previous failures (This used to be commit a44fa5319d87e57f4b904334d9ea65cc6807b789)
2004-12-31 04:17:03 +00:00
const char *fname = BASEDIR "\\lockt7.lck";
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
int fnum1;
r4037: fixed a bunch of "might be uninitialised" warnings after enabling -O1 in my compile (This used to be commit 0928b1f5b68c858922c3ea6c27ed03b5091c6221)
2004-12-02 04:51:56 +00:00
int fnum2 = -1;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
size_t size;
r4063: - change char * -> uint8_t in struct request_buffer - change smbcli_read/write to take void * for the buffers to match read(2)/write(2) all this fixes a lot of gcc-4 warnings metze (This used to be commit b94f92bc6637f748d6f7049f4f9a30b0b8d18a7a)
2004-12-04 13:56:25 +00:00
uint8_t buf[200];
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
bool correct = false;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx, torture_setup_dir(cli1, BASEDIR),
talloc_asprintf(tctx, "Unable to set up %s", BASEDIR));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
fnum1 = smbcli_open(cli1->tree, fname, O_RDWR|O_CREAT|O_EXCL, DENY_NONE);
memset(buf, 0, sizeof(buf));
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx, smbcli_write(cli1->tree, fnum1, 0, buf, 0, sizeof(buf)) == sizeof(buf),
"Failed to create file");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
cli1->session->pid = 1;
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx, smbcli_lock(cli1->tree, fnum1, 130, 4, 0, READ_LOCK),
talloc_asprintf(tctx, "Unable to apply read lock on range 130:4, error was %s",
smbcli_errstr(cli1->tree)));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "pid1 successfully locked range 130:4 for READ\n");
torture_assert(tctx, smbcli_read(cli1->tree, fnum1, buf, 130, 4) == 4,
talloc_asprintf(tctx, "pid1 unable to read the range 130:4, error was %s)",
smbcli_errstr(cli1->tree)));
torture_comment(tctx, "pid1 successfully read the range 130:4\n");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
if (smbcli_write(cli1->tree, fnum1, 0, buf, 130, 4) != 4) {
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "pid1 unable to write to the range 130:4, error was %s\n", smbcli_errstr(cli1->tree));
torture_assert_ntstatus_equal(tctx, smbcli_nt_error(cli1->tree), NT_STATUS_FILE_LOCK_CONFLICT,
"Incorrect error (should be NT_STATUS_FILE_LOCK_CONFLICT)");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
} else {
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_fail(tctx, "pid1 successfully wrote to the range 130:4 (should be denied)");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
}
cli1->session->pid = 2;
if (smbcli_read(cli1->tree, fnum1, buf, 130, 4) != 4) {
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "pid2 unable to read the range 130:4, error was %s\n", smbcli_errstr(cli1->tree));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
} else {
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "pid2 successfully read the range 130:4\n");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
}
if (smbcli_write(cli1->tree, fnum1, 0, buf, 130, 4) != 4) {
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "pid2 unable to write to the range 130:4, error was %s\n", smbcli_errstr(cli1->tree));
torture_assert_ntstatus_equal(tctx, smbcli_nt_error(cli1->tree), NT_STATUS_FILE_LOCK_CONFLICT,
"Incorrect error (should be NT_STATUS_FILE_LOCK_CONFLICT)");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
} else {
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_fail(tctx, "pid2 successfully wrote to the range 130:4 (should be denied)");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
}
cli1->session->pid = 1;
smbcli_unlock(cli1->tree, fnum1, 130, 4);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx, smbcli_lock(cli1->tree, fnum1, 130, 4, 0, WRITE_LOCK),
talloc_asprintf(tctx, "Unable to apply write lock on range 130:4, error was %s",
smbcli_errstr(cli1->tree)));
torture_comment(tctx, "pid1 successfully locked range 130:4 for WRITE\n");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx, smbcli_read(cli1->tree, fnum1, buf, 130, 4) == 4,
talloc_asprintf(tctx, "pid1 unable to read the range 130:4, error was %s",
smbcli_errstr(cli1->tree)));
torture_comment(tctx, "pid1 successfully read the range 130:4\n");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx, smbcli_write(cli1->tree, fnum1, 0, buf, 130, 4) == 4,
talloc_asprintf(tctx, "pid1 unable to write to the range 130:4, error was %s",
smbcli_errstr(cli1->tree)));
torture_comment(tctx, "pid1 successfully wrote to the range 130:4\n");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
cli1->session->pid = 2;
if (smbcli_read(cli1->tree, fnum1, buf, 130, 4) != 4) {
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "pid2 unable to read the range 130:4, error was %s\n",
r3029: implemented byte range lock timeouts. This adds a pvfs_wait_message() routine which uses the new messaging system, event timers and talloc destructors to give a nice generic async event handling system with a easy to use interface. The extensions to pvfs_lock.c are based on calls to pvfs_wait_message() routines. We now pass all of our smbtorture locking tests, although while writing this code I have thought of some additonal tests that should be added, particularly for lock cancel operations. I'll work on that soon. This commit also extends the smbtorture lock tests to test the rather weird 0xEEFFFFFF locking semantics that I have discovered in win2003. Win2003 treats the 0xEEFFFFFF boundary as special, and will give different error codes on either side of it. Locks on both sides are allowed, the only difference is which error code is given when a lock is denied. Anyone like to hazard a guess as to why? It has me stumped. (This used to be commit 4395c0557ab175d6a8dd99df03c266325949ffa5)
2004-10-18 07:40:17 +00:00
smbcli_errstr(cli1->tree));
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_equal(tctx, smbcli_nt_error(cli1->tree), NT_STATUS_FILE_LOCK_CONFLICT,
"Incorrect error (should be NT_STATUS_FILE_LOCK_CONFLICT)");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
} else {
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_fail(tctx, "pid2 successfully read the range 130:4 (should be denied)");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
}
if (smbcli_write(cli1->tree, fnum1, 0, buf, 130, 4) != 4) {
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "pid2 unable to write to the range 130:4, error was %s\n",
r3029: implemented byte range lock timeouts. This adds a pvfs_wait_message() routine which uses the new messaging system, event timers and talloc destructors to give a nice generic async event handling system with a easy to use interface. The extensions to pvfs_lock.c are based on calls to pvfs_wait_message() routines. We now pass all of our smbtorture locking tests, although while writing this code I have thought of some additonal tests that should be added, particularly for lock cancel operations. I'll work on that soon. This commit also extends the smbtorture lock tests to test the rather weird 0xEEFFFFFF locking semantics that I have discovered in win2003. Win2003 treats the 0xEEFFFFFF boundary as special, and will give different error codes on either side of it. Locks on both sides are allowed, the only difference is which error code is given when a lock is denied. Anyone like to hazard a guess as to why? It has me stumped. (This used to be commit 4395c0557ab175d6a8dd99df03c266325949ffa5)
2004-10-18 07:40:17 +00:00
smbcli_errstr(cli1->tree));
r8117: fixed a bunch more dos error code handing. The biggest change was fixing the RAW-CONTEXT test. It was forcing capabilities to zero in an attempt to not negotiated extended security, but as a side effect it was forcing negotiation of dos error codes. This confused the hell out of the test code! Also fixed a bunch of places incorrectly using NT_STATUS_V() instead of NT_STATUS_EQUAL() and several places that had the wrong dos status codes (This used to be commit 0b22744f40804a0d6dc94bfc40ec09306f584f7e)
2005-07-04 05:05:28 +00:00
if (!NT_STATUS_EQUAL(smbcli_nt_error(cli1->tree), NT_STATUS_FILE_LOCK_CONFLICT)) {
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "Incorrect error (should be NT_STATUS_FILE_LOCK_CONFLICT) (%s)\n",
r3029: implemented byte range lock timeouts. This adds a pvfs_wait_message() routine which uses the new messaging system, event timers and talloc destructors to give a nice generic async event handling system with a easy to use interface. The extensions to pvfs_lock.c are based on calls to pvfs_wait_message() routines. We now pass all of our smbtorture locking tests, although while writing this code I have thought of some additonal tests that should be added, particularly for lock cancel operations. I'll work on that soon. This commit also extends the smbtorture lock tests to test the rather weird 0xEEFFFFFF locking semantics that I have discovered in win2003. Win2003 treats the 0xEEFFFFFF boundary as special, and will give different error codes on either side of it. Locks on both sides are allowed, the only difference is which error code is given when a lock is denied. Anyone like to hazard a guess as to why? It has me stumped. (This used to be commit 4395c0557ab175d6a8dd99df03c266325949ffa5)
2004-10-18 07:40:17 +00:00
__location__);
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
goto fail;
}
} else {
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "pid2 successfully wrote to the range 130:4 (should be denied) (%s)\n",
r3029: implemented byte range lock timeouts. This adds a pvfs_wait_message() routine which uses the new messaging system, event timers and talloc destructors to give a nice generic async event handling system with a easy to use interface. The extensions to pvfs_lock.c are based on calls to pvfs_wait_message() routines. We now pass all of our smbtorture locking tests, although while writing this code I have thought of some additonal tests that should be added, particularly for lock cancel operations. I'll work on that soon. This commit also extends the smbtorture lock tests to test the rather weird 0xEEFFFFFF locking semantics that I have discovered in win2003. Win2003 treats the 0xEEFFFFFF boundary as special, and will give different error codes on either side of it. Locks on both sides are allowed, the only difference is which error code is given when a lock is denied. Anyone like to hazard a guess as to why? It has me stumped. (This used to be commit 4395c0557ab175d6a8dd99df03c266325949ffa5)
2004-10-18 07:40:17 +00:00
__location__);
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
goto fail;
}
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "Testing truncate of locked file.\n");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
fnum2 = smbcli_open(cli1->tree, fname, O_RDWR|O_TRUNC, DENY_NONE);
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert(tctx, fnum2 != -1, "Unable to truncate locked file");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_comment(tctx, "Truncated locked file.\n");
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_assert_ntstatus_ok(tctx, smbcli_getatr(cli1->tree, fname, NULL, &size, NULL),
talloc_asprintf(tctx, "getatr failed (%s)", smbcli_errstr(cli1->tree)));
torture_assert(tctx, size == 0, talloc_asprintf(tctx, "Unable to truncate locked file. Size was %u", (unsigned)size));
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
cli1->session->pid = 1;
smbcli_unlock(cli1->tree, fnum1, 130, 4);
r25554: Convert last instances of BOOL, True and False to the standard types. (This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
2007-10-06 22:28:14 +00:00
correct = true;
r3011: separated the locktest code into a separate module in smbtorture (This used to be commit f4a91be63502c0bb32c52c0558dfc7d4d0a21fae)
2004-10-17 02:52:37 +00:00
fail:
smbcli_close(cli1->tree, fnum1);
smbcli_close(cli1->tree, fnum2);
smbcli_unlink(cli1->tree, fname);
return correct;
}
r25000: Fix some more C++ compatibility warnings. (This used to be commit 08bb1ef643ab906f1645cf6f32763dc73b1884e4)
2007-09-07 15:08:14 +00:00
struct torture_suite *torture_base_locktest(TALLOC_CTX *mem_ctx)
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
{
r25000: Fix some more C++ compatibility warnings. (This used to be commit 08bb1ef643ab906f1645cf6f32763dc73b1884e4)
2007-09-07 15:08:14 +00:00
struct torture_suite *suite = torture_suite_create(mem_ctx, "LOCK");
r19339: Merge my 4.0-unittest branch. This adds an API for more fine-grained output in the testsuite rather than just True or False for a set of tests. The aim is to use this for: * known failure lists (run all tests and detect tests that started working or started failing). This would allow us to get rid of the RPC-SAMBA3-* tests * nicer torture output * simplification of the testsuite system * compatibility with other unit testing systems * easier usage of smbtorture (being able to run one test and automatically set up the environment for that) This is still a work-in-progress; expect more updates over the next couple of days. (This used to be commit 0eb6097305776325c75081356309115f445a7218)
2006-10-16 13:06:41 +00:00
torture_suite_add_2smb_test(suite, "LOCK1", torture_locktest1);
torture_suite_add_1smb_test(suite, "LOCK2", torture_locktest2);
torture_suite_add_2smb_test(suite, "LOCK3", torture_locktest3);
torture_suite_add_2smb_test(suite, "LOCK4", torture_locktest4);
torture_suite_add_2smb_test(suite, "LOCK5", torture_locktest5);
torture_suite_add_1smb_test(suite, "LOCK6", torture_locktest6);
torture_suite_add_1smb_test(suite, "LOCK7", torture_locktest7);
return suite;
}
Copy Permalink