| commit | 1c135902213239d04b97449dc3011983a54a683d | |
| author | Stefan Metzmacher <metze@samba.org> | |
| Fri, 6 Dec 2013 12:45:35 +0000 (6 13:45 +0100) | ||
| committer | Karolin Seeger <kseeger@samba.org> | |
| Tue, 1 Apr 2014 07:08:05 +0000 (1 09:08 +0200) | ||
| tree | 27ea1b27509f0ddc3b4116d47c3a67a7c2b44010 | treesnapshot (tar.gz zip) |
| parent | e06ff86a1a3d2f828da88d613f5fe262165671e5 | commitdiff |
s3:smbd: use SMB_BUFFER_SIZE_MIN/MAX to limit lp_max_xmit()
The current limit of 128*1024 causes problems as the value has to be
<= UINT16_MAX otherwise some clients get confused, as they want to
use the MaxBufferSize value from the negprot response (uint32_t)
for the MaxBufferSize value in thet session setup request (uint16_t).
E.g. Windows 7 (as client) sends MaxBufferSize = 0 if the server value
is > UINT16_MAX.
Bug: https://bugzilla.samba.org/show_bug.cgi?id=10422
Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>
(cherry picked from commit a349b0bef9085fd139640ec92399bc63d8029cb9)
The current limit of 128*1024 causes problems as the value has to be
<= UINT16_MAX otherwise some clients get confused, as they want to
use the MaxBufferSize value from the negprot response (uint32_t)
for the MaxBufferSize value in thet session setup request (uint16_t).
E.g. Windows 7 (as client) sends MaxBufferSize = 0 if the server value
is > UINT16_MAX.
Bug: https://bugzilla.samba.org/show_bug.cgi?id=10422
Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>
(cherry picked from commit a349b0bef9085fd139640ec92399bc63d8029cb9)
| source3/smbd/process.c | diffblobblamehistory |