From: Stefan Metzmacher <metze@samba.org>
Date: Tue, 2 Aug 2011 20:59:54 +0000 (+0200)
Subject: s3:torture/*: use CLI_BUFFER_SIZE instead of cli->max_xmit
X-Git-Url: http://git.samba.org/?p=metze%2Fsamba%2Fwip.git;a=commitdiff_plain;h=f69dd6c9d8b0d48f7f0459f9272feebc5e40beb7

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
---

diff --git a/source3/torture/nbench.c b/source3/torture/nbench.c
index d2fddf009453..612dc7db9c51 100644
--- a/source3/torture/nbench.c
+++ b/source3/torture/nbench.c
@@ -298,7 +298,7 @@ static struct tevent_req *nbench_cmd_send(TALLOC_CTX *mem_ctx,
 		}
 		subreq = cli_qpathinfo_send(state, ev, nb_state->cli, fname,
 					    ival(state->cmd->params[2]),
-					    0, nb_state->cli->max_xmit);
+					    0, CLI_BUFFER_SIZE);
 		break;
 	}
 	default:
diff --git a/source3/torture/scanner.c b/source3/torture/scanner.c
index 5edd52d56791..580dadf80e67 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,