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
}
subreq = cli_qpathinfo_send(state, ev, nb_state->cli, fname,
ival(state->cmd->params[2]),
}
subreq = cli_qpathinfo_send(state, ev, nb_state->cli, fname,
ival(state->cmd->params[2]),
- 0, nb_state->cli->max_xmit);
op, 0,
NULL, 0, 0, /* setup */
param, param_len, 2,
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,
NULL, /* recv_flags2 */
NULL, 0, NULL, /* rsetup */
&rparam, 0, rparam_len,
op, 0,
NULL, 0, 0, /* setup */
param, param_len, 2,
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,
NULL, /* recv_flags2 */
NULL, 0, NULL, /* rsetup */
&rparam, 0, rparam_len,