summaryrefslogtreecommitdiff
path: root/source3/libsmb/clilist.c
diff options
context:
space:
mode:
authorStefan Metzmacher <metze@samba.org>2011-08-02 23:05:31 +0200
committerStefan Metzmacher <metze@samba.org>2011-08-09 18:14:38 +0200
commit81e765582bb231a3e182c96777a0eef045095c9a (patch)
treeef866b2baadba9eef827d97ec58e9456d44beb4a /source3/libsmb/clilist.c
parent70c2bbecde434264e0b54279f13159e9991efade (diff)
downloadsamba-81e765582bb231a3e182c96777a0eef045095c9a.tar.gz
samba-81e765582bb231a3e182c96777a0eef045095c9a.tar.bz2
samba-81e765582bb231a3e182c96777a0eef045095c9a.zip
s3:libsmb/cli*: 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 <metze@samba.org> Autobuild-Date: Tue Aug 9 18:14:38 CEST 2011 on sn-devel-104
Diffstat (limited to 'source3/libsmb/clilist.c')
-rw-r--r--source3/libsmb/clilist.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/source3/libsmb/clilist.c b/source3/libsmb/clilist.c
index ba3dd2b2b5..ac10795920 100644
--- a/source3/libsmb/clilist.c
+++ b/source3/libsmb/clilist.c
@@ -599,7 +599,7 @@ static struct tevent_req *cli_list_trans_send(TALLOC_CTX *mem_ctx,
SMBtrans2, NULL, -1, 0, 0,
state->setup, 1, 0,
state->param, param_len, 10,
- NULL, 0, cli->max_xmit);
+ NULL, 0, CLI_BUFFER_SIZE);
if (tevent_req_nomem(subreq, req)) {
return tevent_req_post(req, ev);
}
@@ -783,7 +783,7 @@ static void cli_list_trans_done(struct tevent_req *subreq)
SMBtrans2, NULL, -1, 0, 0,
state->setup, 1, 0,
state->param, param_len, 10,
- NULL, 0, state->cli->max_xmit);
+ NULL, 0, CLI_BUFFER_SIZE);
if (tevent_req_nomem(subreq, req)) {
return;
}