Date: Wed, 11 Nov 2015 20:38:39 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 204438] setsockopt() handling of kern.ipc.maxsockbuf limit Message-ID: <bug-204438-2472-6LpqjWbmq5@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-204438-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-204438-2472@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204438 --- Comment #6 from Cameron Sparr <cameronsparr@gmail.com> --- Created attachment 163023 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163023&action=edit Patch of the diff in the URL section. Changes behavior of setsockopt This change makes it so that the setsockopt() function does not error when a user passes a value for SO_RCVBUF equal or under the maximim (kern.ipc.maxsockbuf). Currently the behavior is to error if the value is greater than the _adjusted_ max, which on amd64 turns out to be something like kern.ipc.maxsockbuf * 0.889 This is confusing for users, and this change will set the value passed to the adjusted max if the value is greater than the adjusted and less than the actual max. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204438-2472-6LpqjWbmq5>