Date: Mon, 16 Nov 2015 16:29:30 +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-gGhXHoBX4u@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 #18 from Cameron Sparr <cameronsparr@gmail.com> --- @Alfred, I guess on Linux there is no way to warn about that, users would have to check the buffer size limits themselves. In conclusion, should I change my patch to do what you originally suggested? Which is to have kern.ipc.maxsockbuf represent that maximum amount of DATA that the socket can handle? -- 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-gGhXHoBX4u>