From 924b2d5b7fdfc562765ffe7181ffb479bb05ae84 Mon Sep 17 00:00:00 2001 From: Stefan Metzmacher Date: Tue, 13 Sep 2011 13:12:09 +0200 Subject: 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 Autobuild-User: Stefan Metzmacher Autobuild-Date: Tue Sep 13 14:52:35 CEST 2011 on sn-devel-104 --- source3/torture/torture.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'source3/torture') diff --git a/source3/torture/torture.c b/source3/torture/torture.c index 0cba5c7172..d791684de6 100644 --- a/source3/torture/torture.c +++ b/source3/torture/torture.c @@ -3436,7 +3436,7 @@ static NTSTATUS new_trans(struct cli_state *pcli, int fnum, int level) NTSTATUS status; status = cli_qfileinfo(talloc_tos(), pcli, fnum, level, 0, - pcli->max_xmit, NULL, &buf, &len); + CLI_BUFFER_SIZE, NULL, &buf, &len); if (!NT_STATUS_IS_OK(status)) { printf("ERROR: qfileinfo (%d) failed (%s)\n", level, nt_errstr(status)); -- cgit