sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-11 05:18:09 +03:00
Code
33647bd841
samba-mirror/source4/torture/raw/notify.c

221 lines
7.1 KiB
C
Raw Normal View History

first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
/*
Unix SMB/CIFS implementation.
basic raw test suite for change notify
Copyright (C) Andrew Tridgell 2003
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
the Free Software Foundation; either version 2 of the License, or
(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
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
*/
#include "includes.h"
r12693: Move core data structures out of smb.h into core.h torture prototypes in seperate header (This used to be commit 73610639b23ca3743077193fa0b1de7c7f65944d)
2006-01-03 16:41:17 +03:00
#include "torture/torture.h"
r12542: Move some more prototypes out to seperate headers (This used to be commit 0aca5fd5130d980d07398f3291d294202aefe3c2)
2005-12-28 18:38:36 +03:00
#include "libcli/raw/libcliraw.h"
r12694: Move some headers to the directory of the subsystem they belong to. (This used to be commit c722f665c90103f3ed57621c460e32ad33e7a8a3)
2006-01-03 18:40:05 +03:00
#include "libcli/libcli.h"
r14059: change notify is quite a bit more complex than we thought. These tests show that w2k3 buffers notifies on directories where you have used notify previously, thus giving you notifications on events that happen even when you do not have a current notify call outstanding. This makes it much easier for clients to avoid race conditions, which is probably why it is done. It also means that associating change notifies in Samba with outstanding change notify requests won't work - instead we have to associate them with buffers on open directories. (This used to be commit 8c5c8846f58c3f4b852c27dcecea8dfe21da58b6)
2006-03-09 06:52:10 +03:00
#include "system/filesys.h"
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
#define BASEDIR "\\test_notify"
#define CHECK_STATUS(status, correct) do { \
if (!NT_STATUS_EQUAL(status, correct)) { \
printf("(%d) Incorrect status %s - should be %s\n", \
__LINE__, nt_errstr(status), nt_errstr(correct)); \
ret = False; \
goto done; \
}} while (0)
#define CHECK_VAL(v, correct) do { \
if ((v) != (correct)) { \
r14059: change notify is quite a bit more complex than we thought. These tests show that w2k3 buffers notifies on directories where you have used notify previously, thus giving you notifications on events that happen even when you do not have a current notify call outstanding. This makes it much easier for clients to avoid race conditions, which is probably why it is done. It also means that associating change notifies in Samba with outstanding change notify requests won't work - instead we have to associate them with buffers on open directories. (This used to be commit 8c5c8846f58c3f4b852c27dcecea8dfe21da58b6)
2006-03-09 06:52:10 +03:00
printf("(%d) wrong value for %s 0x%x should be 0x%x\n", \
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
__LINE__, #v, (int)v, (int)correct); \
ret = False; \
goto done; \
}} while (0)
#define CHECK_WSTR(field, value, flags) do { \
r1740: fixed the torture suite for ASCII-only servers (This used to be commit c3bce90be745db3e7cbf8273c1c8496920332f5e)
2004-08-12 01:11:37 +04:00
if (!field.s || strcmp(field.s, value) || wire_bad_flags(&field, flags, cli)) { \
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
printf("(%d) %s [%s] != %s\n", __LINE__, #field, field.s, value); \
ret = False; \
goto done; \
}} while (0)
/*
basic testing of change notify
*/
r3324: made the smbtorture code completely warning free (This used to be commit 7067bb9b52223cafa28470f264f0b60646a07a01)
2004-10-28 17:40:50 +04:00
BOOL torture_raw_notify(void)
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
{
r1654: rename cli_ -> smbcli_ rename CLI_ -> SMBCLI_ metze (This used to be commit 8441750fd9427dd6fe477f27e603821b4026f038)
2004-08-04 17:23:35 +04:00
struct smbcli_state *cli;
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
BOOL ret = True;
TALLOC_CTX *mem_ctx;
NTSTATUS status;
r14173: change smb interface structures to always use a union smb_file, to abtract - const char *path fot qpathinfo and setpathinfo - uint16_t fnum for SMB - smb2_handle handle for SMB2 the idea is to later add a struct ntvfs_handle *ntvfs so that the ntvfs subsystem don't need to know the difference between SMB and SMB2 metze (This used to be commit 2ef3f5970901b5accdb50f0d0115b5d46b0c788f)
2006-03-10 23:49:20 +03:00
union smb_notify notify;
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
union smb_open io;
r14059: change notify is quite a bit more complex than we thought. These tests show that w2k3 buffers notifies on directories where you have used notify previously, thus giving you notifications on events that happen even when you do not have a current notify call outstanding. This makes it much easier for clients to avoid race conditions, which is probably why it is done. It also means that associating change notifies in Samba with outstanding change notify requests won't work - instead we have to associate them with buffers on open directories. (This used to be commit 8c5c8846f58c3f4b852c27dcecea8dfe21da58b6)
2006-03-09 06:52:10 +03:00
int i, count, fnum, fnum2;
struct smbcli_request *req, *req2;
extern int torture_numops;
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
if (!torture_open_connection(&cli)) {
return False;
}
mem_ctx = talloc_init("torture_raw_notify");
r3699: - split the delayed write testing out of RAW-WRITE, as it is not yet clear what the correct behaviour is for delayed stat info update. - use a common torture_setup_dir() function for setting up a test directory in torture tests. (This used to be commit f7fb34715b7d6ea3c35ddd684cfb27459a420339)
2004-11-12 12:37:59 +03:00
if (!torture_setup_dir(cli, BASEDIR)) {
return False;
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
}
/*
get a handle on the directory
*/
io.generic.level = RAW_OPEN_NTCREATEX;
io.ntcreatex.in.root_fid = 0;
io.ntcreatex.in.flags = 0;
r4011: get rid of rpc_secdes.h and replace it with a single sane set of definitions for security access masks, in security.idl The previous definitions were inconsistently named, and contained many duplicate and misleading entries. I kept finding myself tripping up while using them. (This used to be commit 01c0fa722f80ceeb3f81f01987de95f365a2ed3d)
2004-11-30 07:33:27 +03:00
io.ntcreatex.in.access_mask = SEC_FILE_ALL;
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
io.ntcreatex.in.create_options = NTCREATEX_OPTIONS_DIRECTORY;
io.ntcreatex.in.file_attr = FILE_ATTRIBUTE_NORMAL;
io.ntcreatex.in.share_access = NTCREATEX_SHARE_ACCESS_READ | NTCREATEX_SHARE_ACCESS_WRITE;
io.ntcreatex.in.alloc_size = 0;
r8123: fixed the RAW-NOTIFY and RAW-QFSINFO tests against w2k3 (This used to be commit acd9fad3a4c578e20cd4bdb79a000a7ff70f680c)
2005-07-04 09:54:09 +04:00
io.ntcreatex.in.open_disposition = NTCREATEX_DISP_OPEN;
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
io.ntcreatex.in.impersonation = NTCREATEX_IMPERSONATION_ANONYMOUS;
io.ntcreatex.in.security_flags = 0;
io.ntcreatex.in.fname = BASEDIR;
status = smb_raw_open(cli->tree, mem_ctx, &io);
CHECK_STATUS(status, NT_STATUS_OK);
r14173: change smb interface structures to always use a union smb_file, to abtract - const char *path fot qpathinfo and setpathinfo - uint16_t fnum for SMB - smb2_handle handle for SMB2 the idea is to later add a struct ntvfs_handle *ntvfs so that the ntvfs subsystem don't need to know the difference between SMB and SMB2 metze (This used to be commit 2ef3f5970901b5accdb50f0d0115b5d46b0c788f)
2006-03-10 23:49:20 +03:00
fnum = io.ntcreatex.file.fnum;
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
r14059: change notify is quite a bit more complex than we thought. These tests show that w2k3 buffers notifies on directories where you have used notify previously, thus giving you notifications on events that happen even when you do not have a current notify call outstanding. This makes it much easier for clients to avoid race conditions, which is probably why it is done. It also means that associating change notifies in Samba with outstanding change notify requests won't work - instead we have to associate them with buffers on open directories. (This used to be commit 8c5c8846f58c3f4b852c27dcecea8dfe21da58b6)
2006-03-09 06:52:10 +03:00
status = smb_raw_open(cli->tree, mem_ctx, &io);
CHECK_STATUS(status, NT_STATUS_OK);
r14173: change smb interface structures to always use a union smb_file, to abtract - const char *path fot qpathinfo and setpathinfo - uint16_t fnum for SMB - smb2_handle handle for SMB2 the idea is to later add a struct ntvfs_handle *ntvfs so that the ntvfs subsystem don't need to know the difference between SMB and SMB2 metze (This used to be commit 2ef3f5970901b5accdb50f0d0115b5d46b0c788f)
2006-03-10 23:49:20 +03:00
fnum2 = io.ntcreatex.file.fnum;
r14059: change notify is quite a bit more complex than we thought. These tests show that w2k3 buffers notifies on directories where you have used notify previously, thus giving you notifications on events that happen even when you do not have a current notify call outstanding. This makes it much easier for clients to avoid race conditions, which is probably why it is done. It also means that associating change notifies in Samba with outstanding change notify requests won't work - instead we have to associate them with buffers on open directories. (This used to be commit 8c5c8846f58c3f4b852c27dcecea8dfe21da58b6)
2006-03-09 06:52:10 +03:00
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
/* ask for a change notify */
r14173: change smb interface structures to always use a union smb_file, to abtract - const char *path fot qpathinfo and setpathinfo - uint16_t fnum for SMB - smb2_handle handle for SMB2 the idea is to later add a struct ntvfs_handle *ntvfs so that the ntvfs subsystem don't need to know the difference between SMB and SMB2 metze (This used to be commit 2ef3f5970901b5accdb50f0d0115b5d46b0c788f)
2006-03-10 23:49:20 +03:00
notify.notify.in.buffer_size = 1000;
notify.notify.in.completion_filter = 0x3;
notify.notify.file.fnum = fnum;
notify.notify.in.recursive = True;
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
printf("testing notify mkdir\n");
req = smb_raw_changenotify_send(cli->tree, &notify);
r1654: rename cli_ -> smbcli_ rename CLI_ -> SMBCLI_ metze (This used to be commit 8441750fd9427dd6fe477f27e603821b4026f038)
2004-08-04 17:23:35 +04:00
smbcli_mkdir(cli->tree, BASEDIR "\\subdir-name");
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
status = smb_raw_changenotify_recv(req, mem_ctx, &notify);
CHECK_STATUS(status, NT_STATUS_OK);
r14173: change smb interface structures to always use a union smb_file, to abtract - const char *path fot qpathinfo and setpathinfo - uint16_t fnum for SMB - smb2_handle handle for SMB2 the idea is to later add a struct ntvfs_handle *ntvfs so that the ntvfs subsystem don't need to know the difference between SMB and SMB2 metze (This used to be commit 2ef3f5970901b5accdb50f0d0115b5d46b0c788f)
2006-03-10 23:49:20 +03:00
CHECK_VAL(notify.notify.out.num_changes, 1);
CHECK_VAL(notify.notify.out.changes[0].action, NOTIFY_ACTION_ADDED);
CHECK_WSTR(notify.notify.out.changes[0].name, "subdir-name", STR_UNICODE);
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
printf("testing notify rmdir\n");
req = smb_raw_changenotify_send(cli->tree, &notify);
r1654: rename cli_ -> smbcli_ rename CLI_ -> SMBCLI_ metze (This used to be commit 8441750fd9427dd6fe477f27e603821b4026f038)
2004-08-04 17:23:35 +04:00
smbcli_rmdir(cli->tree, BASEDIR "\\subdir-name");
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
status = smb_raw_changenotify_recv(req, mem_ctx, &notify);
CHECK_STATUS(status, NT_STATUS_OK);
r14173: change smb interface structures to always use a union smb_file, to abtract - const char *path fot qpathinfo and setpathinfo - uint16_t fnum for SMB - smb2_handle handle for SMB2 the idea is to later add a struct ntvfs_handle *ntvfs so that the ntvfs subsystem don't need to know the difference between SMB and SMB2 metze (This used to be commit 2ef3f5970901b5accdb50f0d0115b5d46b0c788f)
2006-03-10 23:49:20 +03:00
CHECK_VAL(notify.notify.out.num_changes, 1);
CHECK_VAL(notify.notify.out.changes[0].action, NOTIFY_ACTION_REMOVED);
CHECK_WSTR(notify.notify.out.changes[0].name, "subdir-name", STR_UNICODE);
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
printf("testing notify cancel\n");
req = smb_raw_changenotify_send(cli->tree, &notify);
smb_raw_ntcancel(req);
r1654: rename cli_ -> smbcli_ rename CLI_ -> SMBCLI_ metze (This used to be commit 8441750fd9427dd6fe477f27e603821b4026f038)
2004-08-04 17:23:35 +04:00
smbcli_mkdir(cli->tree, BASEDIR "\\subdir-name");
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
status = smb_raw_changenotify_recv(req, mem_ctx, &notify);
CHECK_STATUS(status, NT_STATUS_CANCELLED);
r14059: change notify is quite a bit more complex than we thought. These tests show that w2k3 buffers notifies on directories where you have used notify previously, thus giving you notifications on events that happen even when you do not have a current notify call outstanding. This makes it much easier for clients to avoid race conditions, which is probably why it is done. It also means that associating change notifies in Samba with outstanding change notify requests won't work - instead we have to associate them with buffers on open directories. (This used to be commit 8c5c8846f58c3f4b852c27dcecea8dfe21da58b6)
2006-03-09 06:52:10 +03:00
count = torture_numops;
printf("testing buffered notify on create of %d files\n", count);
for (i=0;i<count;i++) {
char *fname = talloc_asprintf(cli, BASEDIR "\\test%d.txt", i);
int fnum3 = smbcli_open(cli->tree, fname, O_CREAT|O_RDWR, DENY_NONE);
if (fnum3 == -1) {
printf("Failed to create %s - %s\n",
fname, smbcli_errstr(cli->tree));
ret = False;
goto done;
}
talloc_free(fname);
smbcli_close(cli->tree, fnum3);
}
/* setup a new notify on a different directory handle. This
new notify won't see the events above. */
r14173: change smb interface structures to always use a union smb_file, to abtract - const char *path fot qpathinfo and setpathinfo - uint16_t fnum for SMB - smb2_handle handle for SMB2 the idea is to later add a struct ntvfs_handle *ntvfs so that the ntvfs subsystem don't need to know the difference between SMB and SMB2 metze (This used to be commit 2ef3f5970901b5accdb50f0d0115b5d46b0c788f)
2006-03-10 23:49:20 +03:00
notify.notify.file.fnum = fnum2;
r14059: change notify is quite a bit more complex than we thought. These tests show that w2k3 buffers notifies on directories where you have used notify previously, thus giving you notifications on events that happen even when you do not have a current notify call outstanding. This makes it much easier for clients to avoid race conditions, which is probably why it is done. It also means that associating change notifies in Samba with outstanding change notify requests won't work - instead we have to associate them with buffers on open directories. (This used to be commit 8c5c8846f58c3f4b852c27dcecea8dfe21da58b6)
2006-03-09 06:52:10 +03:00
req2 = smb_raw_changenotify_send(cli->tree, &notify);
/* whereas this notify will see the above buffered events as
well */
r14173: change smb interface structures to always use a union smb_file, to abtract - const char *path fot qpathinfo and setpathinfo - uint16_t fnum for SMB - smb2_handle handle for SMB2 the idea is to later add a struct ntvfs_handle *ntvfs so that the ntvfs subsystem don't need to know the difference between SMB and SMB2 metze (This used to be commit 2ef3f5970901b5accdb50f0d0115b5d46b0c788f)
2006-03-10 23:49:20 +03:00
notify.notify.file.fnum = fnum;
r14059: change notify is quite a bit more complex than we thought. These tests show that w2k3 buffers notifies on directories where you have used notify previously, thus giving you notifications on events that happen even when you do not have a current notify call outstanding. This makes it much easier for clients to avoid race conditions, which is probably why it is done. It also means that associating change notifies in Samba with outstanding change notify requests won't work - instead we have to associate them with buffers on open directories. (This used to be commit 8c5c8846f58c3f4b852c27dcecea8dfe21da58b6)
2006-03-09 06:52:10 +03:00
req = smb_raw_changenotify_send(cli->tree, &notify);
status = smbcli_unlink(cli->tree, BASEDIR "\\test0.txt");
CHECK_STATUS(status, NT_STATUS_OK);
/* receive the reply from the 2nd notify */
status = smb_raw_changenotify_recv(req, mem_ctx, &notify);
CHECK_STATUS(status, NT_STATUS_OK);
r14173: change smb interface structures to always use a union smb_file, to abtract - const char *path fot qpathinfo and setpathinfo - uint16_t fnum for SMB - smb2_handle handle for SMB2 the idea is to later add a struct ntvfs_handle *ntvfs so that the ntvfs subsystem don't need to know the difference between SMB and SMB2 metze (This used to be commit 2ef3f5970901b5accdb50f0d0115b5d46b0c788f)
2006-03-10 23:49:20 +03:00
CHECK_VAL(notify.notify.out.num_changes, count+1);
for (i=0;i<notify.notify.out.num_changes;i++) {
CHECK_VAL(notify.notify.out.changes[i].action, NOTIFY_ACTION_ADDED);
r14059: change notify is quite a bit more complex than we thought. These tests show that w2k3 buffers notifies on directories where you have used notify previously, thus giving you notifications on events that happen even when you do not have a current notify call outstanding. This makes it much easier for clients to avoid race conditions, which is probably why it is done. It also means that associating change notifies in Samba with outstanding change notify requests won't work - instead we have to associate them with buffers on open directories. (This used to be commit 8c5c8846f58c3f4b852c27dcecea8dfe21da58b6)
2006-03-09 06:52:10 +03:00
}
r14173: change smb interface structures to always use a union smb_file, to abtract - const char *path fot qpathinfo and setpathinfo - uint16_t fnum for SMB - smb2_handle handle for SMB2 the idea is to later add a struct ntvfs_handle *ntvfs so that the ntvfs subsystem don't need to know the difference between SMB and SMB2 metze (This used to be commit 2ef3f5970901b5accdb50f0d0115b5d46b0c788f)
2006-03-10 23:49:20 +03:00
CHECK_WSTR(notify.notify.out.changes[0].name, "subdir-name", STR_UNICODE);
r14059: change notify is quite a bit more complex than we thought. These tests show that w2k3 buffers notifies on directories where you have used notify previously, thus giving you notifications on events that happen even when you do not have a current notify call outstanding. This makes it much easier for clients to avoid race conditions, which is probably why it is done. It also means that associating change notifies in Samba with outstanding change notify requests won't work - instead we have to associate them with buffers on open directories. (This used to be commit 8c5c8846f58c3f4b852c27dcecea8dfe21da58b6)
2006-03-09 06:52:10 +03:00
/* and now from the 1st notify */
status = smb_raw_changenotify_recv(req2, mem_ctx, &notify);
CHECK_STATUS(status, NT_STATUS_OK);
r14173: change smb interface structures to always use a union smb_file, to abtract - const char *path fot qpathinfo and setpathinfo - uint16_t fnum for SMB - smb2_handle handle for SMB2 the idea is to later add a struct ntvfs_handle *ntvfs so that the ntvfs subsystem don't need to know the difference between SMB and SMB2 metze (This used to be commit 2ef3f5970901b5accdb50f0d0115b5d46b0c788f)
2006-03-10 23:49:20 +03:00
CHECK_VAL(notify.notify.out.num_changes, 1);
r14059: change notify is quite a bit more complex than we thought. These tests show that w2k3 buffers notifies on directories where you have used notify previously, thus giving you notifications on events that happen even when you do not have a current notify call outstanding. This makes it much easier for clients to avoid race conditions, which is probably why it is done. It also means that associating change notifies in Samba with outstanding change notify requests won't work - instead we have to associate them with buffers on open directories. (This used to be commit 8c5c8846f58c3f4b852c27dcecea8dfe21da58b6)
2006-03-09 06:52:10 +03:00
printf("testing notify on wildcard unlink for %d files\n", count);
req = smb_raw_changenotify_send(cli->tree, &notify);
status = smbcli_unlink(cli->tree, BASEDIR "\\test*.txt");
CHECK_STATUS(status, NT_STATUS_OK);
status = smb_raw_changenotify_recv(req, mem_ctx, &notify);
CHECK_STATUS(status, NT_STATUS_OK);
r14173: change smb interface structures to always use a union smb_file, to abtract - const char *path fot qpathinfo and setpathinfo - uint16_t fnum for SMB - smb2_handle handle for SMB2 the idea is to later add a struct ntvfs_handle *ntvfs so that the ntvfs subsystem don't need to know the difference between SMB and SMB2 metze (This used to be commit 2ef3f5970901b5accdb50f0d0115b5d46b0c788f)
2006-03-10 23:49:20 +03:00
CHECK_VAL(notify.notify.out.num_changes, 1);
CHECK_VAL(notify.notify.out.changes[0].action, NOTIFY_ACTION_REMOVED);
CHECK_WSTR(notify.notify.out.changes[0].name, "test0.txt", STR_UNICODE);
r14059: change notify is quite a bit more complex than we thought. These tests show that w2k3 buffers notifies on directories where you have used notify previously, thus giving you notifications on events that happen even when you do not have a current notify call outstanding. This makes it much easier for clients to avoid race conditions, which is probably why it is done. It also means that associating change notifies in Samba with outstanding change notify requests won't work - instead we have to associate them with buffers on open directories. (This used to be commit 8c5c8846f58c3f4b852c27dcecea8dfe21da58b6)
2006-03-09 06:52:10 +03:00
/* and we now see the rest of the unlink calls */
req = smb_raw_changenotify_send(cli->tree, &notify);
status = smb_raw_changenotify_recv(req, mem_ctx, &notify);
CHECK_STATUS(status, NT_STATUS_OK);
r14173: change smb interface structures to always use a union smb_file, to abtract - const char *path fot qpathinfo and setpathinfo - uint16_t fnum for SMB - smb2_handle handle for SMB2 the idea is to later add a struct ntvfs_handle *ntvfs so that the ntvfs subsystem don't need to know the difference between SMB and SMB2 metze (This used to be commit 2ef3f5970901b5accdb50f0d0115b5d46b0c788f)
2006-03-10 23:49:20 +03:00
CHECK_VAL(notify.notify.out.num_changes, count-1);
for (i=0;i<notify.notify.out.num_changes;i++) {
CHECK_VAL(notify.notify.out.changes[i].action, NOTIFY_ACTION_REMOVED);
r14059: change notify is quite a bit more complex than we thought. These tests show that w2k3 buffers notifies on directories where you have used notify previously, thus giving you notifications on events that happen even when you do not have a current notify call outstanding. This makes it much easier for clients to avoid race conditions, which is probably why it is done. It also means that associating change notifies in Samba with outstanding change notify requests won't work - instead we have to associate them with buffers on open directories. (This used to be commit 8c5c8846f58c3f4b852c27dcecea8dfe21da58b6)
2006-03-09 06:52:10 +03:00
}
r14173: change smb interface structures to always use a union smb_file, to abtract - const char *path fot qpathinfo and setpathinfo - uint16_t fnum for SMB - smb2_handle handle for SMB2 the idea is to later add a struct ntvfs_handle *ntvfs so that the ntvfs subsystem don't need to know the difference between SMB and SMB2 metze (This used to be commit 2ef3f5970901b5accdb50f0d0115b5d46b0c788f)
2006-03-10 23:49:20 +03:00
notify.notify.file.fnum = fnum2;
r14059: change notify is quite a bit more complex than we thought. These tests show that w2k3 buffers notifies on directories where you have used notify previously, thus giving you notifications on events that happen even when you do not have a current notify call outstanding. This makes it much easier for clients to avoid race conditions, which is probably why it is done. It also means that associating change notifies in Samba with outstanding change notify requests won't work - instead we have to associate them with buffers on open directories. (This used to be commit 8c5c8846f58c3f4b852c27dcecea8dfe21da58b6)
2006-03-09 06:52:10 +03:00
req = smb_raw_changenotify_send(cli->tree, &notify);
status = smb_raw_changenotify_recv(req, mem_ctx, &notify);
CHECK_STATUS(status, NT_STATUS_OK);
r14173: change smb interface structures to always use a union smb_file, to abtract - const char *path fot qpathinfo and setpathinfo - uint16_t fnum for SMB - smb2_handle handle for SMB2 the idea is to later add a struct ntvfs_handle *ntvfs so that the ntvfs subsystem don't need to know the difference between SMB and SMB2 metze (This used to be commit 2ef3f5970901b5accdb50f0d0115b5d46b0c788f)
2006-03-10 23:49:20 +03:00
CHECK_VAL(notify.notify.out.num_changes, count-1);
for (i=0;i<notify.notify.out.num_changes;i++) {
CHECK_VAL(notify.notify.out.changes[i].action, NOTIFY_ACTION_REMOVED);
r14059: change notify is quite a bit more complex than we thought. These tests show that w2k3 buffers notifies on directories where you have used notify previously, thus giving you notifications on events that happen even when you do not have a current notify call outstanding. This makes it much easier for clients to avoid race conditions, which is probably why it is done. It also means that associating change notifies in Samba with outstanding change notify requests won't work - instead we have to associate them with buffers on open directories. (This used to be commit 8c5c8846f58c3f4b852c27dcecea8dfe21da58b6)
2006-03-09 06:52:10 +03:00
}
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
done:
smb_raw_exit(cli->session);
r1654: rename cli_ -> smbcli_ rename CLI_ -> SMBCLI_ metze (This used to be commit 8441750fd9427dd6fe477f27e603821b4026f038)
2004-08-04 17:23:35 +04:00
smbcli_deltree(cli->tree, BASEDIR);
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
torture_close_connection(cli);
r5037: got rid of all of the TALLOC_DEPRECATED stuff. My apologies for the large commit. I thought this was worthwhile to get done for consistency. (This used to be commit ec32b22ed5ec224f6324f5e069d15e92e38e15c0)
2005-01-27 10:08:20 +03:00
talloc_free(mem_ctx);
first public release of samba4 code (This used to be commit b0510b5428b3461aeb9bbe3cc95f62fc73e2b97f)
2003-08-13 05:53:07 +04:00
return ret;
}
Copy Permalink