git.samba.org / metze / samba / wip.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: f69dd6c) | patch
s3:libsmb/cli*: use CLI_BUFFER_SIZE instead of cli->max_xmit
authorStefan Metzmacher <metze@samba.org>
Tue, 2 Aug 2011 21:05:31 +0000 (23:05 +0200)
committerStefan Metzmacher <metze@samba.org>
Tue, 2 Aug 2011 21:15:14 +0000 (23:15 +0200)
commit7e2d0f92fc44765bea9f3153239cdfaff36349af
tree9955dc7e6bc60e6d4c8ae52bda73ae08724027f3tree
parentf69dd6c9d8b0d48f7f0459f9272feebc5e40beb7commit | diff
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
source3/libsmb/clidfs.c diff | blob | history
source3/libsmb/clifile.c diff | blob | history
source3/libsmb/clilist.c diff | blob | history
source3/libsmb/clirap.c diff | blob | history
Work in progress branches