rap: trans->in.max_data should not depend on the smb max size

We now support async multi fragment SMBtrans calls.

metze
(This used to be commit 66e0c1754f14cf0100ca2d3e9c0cd8c87f9dc1e6)

diff --git a/source4/torture/rap/rap.c b/source4/torture/rap/rap.c
index 1ccd1254dddc4f996777029867659fdd9b92d4ed..e93bd52b9a7d6586b59fc3ea4c062566eaf5705c 100644 (file)
--- a/source4/torture/rap/rap.c
+++ b/source4/torture/rap/rap.c
@@ -206,7 +206,7 @@ static NTSTATUS rap_cli_do_call(struct smbcli_tree *tree,
        params->flags = RAPNDR_FLAGS;
 
        trans.in.max_param = call->rcv_paramlen;
-       trans.in.max_data = smb_raw_max_trans_data(tree, call->rcv_paramlen);
+       trans.in.max_data = call->rcv_datalen;
        trans.in.max_setup = 0;
        trans.in.flags = 0;
        trans.in.timeout = 0;