summaryrefslogtreecommitdiffstats
path: root/secure
diff options
context:
space:
mode:
authorian <ian@FreeBSD.org>2013-11-13 01:01:15 +0000
committerian <ian@FreeBSD.org>2013-11-13 01:01:15 +0000
commitdc4eaa7b21ac5fbd8a836c7365ec66f8c991496c (patch)
tree5d932af4b3e236816ce0a12f974536b7aea669fc /secure
parent384d86e8883acf1387f02c9f3ec34798f973dd62 (diff)
downloadFreeBSD-src-dc4eaa7b21ac5fbd8a836c7365ec66f8c991496c.zip
FreeBSD-src-dc4eaa7b21ac5fbd8a836c7365ec66f8c991496c.tar.gz
This fixes 3 problems in syslogd related to sizing receive buffers...
- A call was misplaced at the wrong level of nested if blocks, so that the buffers for unix domain sockets (/dev/log, /dev/klog) were never increased at all; they remained at a way-too-small default size of 4096. - The function that was supposed to double the size of the buffer sometimes did nothing, and sometimes installed a wildly-wrong buffer size (either too large or too small) due to an unitialized 'slen' variable passed to getsockopt(). Most often it doubled the UDP buffers from 40k to 80k because accidentally there would be harmless stack garbage in the unitialized variables. - The whole concept of blindly doubling a socket's buffer size without knowing what size it started at is a design flaw that has to be called a bug. If the double_rbuf() function had worked at all (I.E., if the other two bugs didn't exist) this would lead to UDP sockets having an 80k buffer while unix dgram sockets get an 8k buffer. There's nothing about the problem being solved that requires larger buffers for UDP than for unix dgram sockets -- the buffering requirements are the same regardless of socket type. This change renames the double_rbuf() function to increase_rbuf() and increases the buffer size on all types of sockets to 80k. 80k was chosen only because it appears to be the size the original change was shooting for, and it certainly seems to be reasonably large (I might have picked 64k in the absence of any historical guidance). PR: 160433 Submitted by: me, in 2011.
Diffstat (limited to 'secure')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud