diff options
| author | Stefan Metzmacher <metze@samba.org> | 2011-08-02 22:59:54 +0200 |
|---|---|---|
| committer | Stefan Metzmacher <metze@samba.org> | 2011-08-09 15:30:04 +0200 |
| commit | 70c2bbecde434264e0b54279f13159e9991efade (patch) | |
| tree | f01a9018a7114d51192fc327d84d06e419291f7b /source3/torture/scanner.c | |
| parent | 46eacae8b516c0a2b9c372af0baadc436f64d957 (diff) | |
| download | samba-70c2bbecde434264e0b54279f13159e9991efade.tar.gz samba-70c2bbecde434264e0b54279f13159e9991efade.tar.bz2 samba-70c2bbecde434264e0b54279f13159e9991efade.zip | |
s3:torture/*: use CLI_BUFFER_SIZE instead of cli->max_xmit
The max_data parameter of trans2/nttrans calls are not bound
to cli->max_xmit. Even with cli->max_xmit, which means the max
size of the whole SMB pdu, we would get fragmented trans2/nttrans
replies. That's why we can also use our maximum, which is CLI_BUFFER_SIZE.
metze
Diffstat (limited to 'source3/torture/scanner.c')
| -rw-r--r-- | source3/torture/scanner.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/source3/torture/scanner.c b/source3/torture/scanner.c index 5edd52d567..580dadf80e 100644 --- a/source3/torture/scanner.c +++ b/source3/torture/scanner.c @@ -67,7 +67,7 @@ static NTSTATUS try_trans2(struct cli_state *cli, op, 0, NULL, 0, 0, /* setup */ param, param_len, 2, - data, data_len, cli->max_xmit, + data, data_len, CLI_BUFFER_SIZE, NULL, /* recv_flags2 */ NULL, 0, NULL, /* rsetup */ &rparam, 0, rparam_len, @@ -313,7 +313,7 @@ static NTSTATUS try_nttrans(struct cli_state *cli, op, 0, NULL, 0, 0, /* setup */ param, param_len, 2, - data, data_len, cli->max_xmit, + data, data_len, CLI_BUFFER_SIZE, NULL, /* recv_flags2 */ NULL, 0, NULL, /* rsetup */ &rparam, 0, rparam_len, |