Date: Tue, 4 Mar 2003 04:31:30 +0200
From: Alexey Zelkin <phantom@FreeBSD.org.ua>
To: Garrett Wollman <wollman@lcs.mit.edu>
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: maxsockbuf is useless value {?|:-(}
Message-ID: <20030304043130.B42396@phantom.cris.net>
In-Reply-To: <200303040212.h242C5fI001303@khavrinen.lcs.mit.edu>; from wollman@lcs.mit.edu on Mon, Mar 03, 2003 at 09:12:05PM -0500
References: <20030228130621.A16504@phantom.cris.net> <200302281931.h1SJVAUg060319@khavrinen.lcs.mit.edu> <20030301134118.GE77007@sunbay.com> <200303022015.h22KFbn0075585@khavrinen.lcs.mit.edu> <20030304040434.A42256@phantom.cris.net> <200303040212.h242C5fI001303@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
hi, On Mon, Mar 03, 2003 at 09:12:05PM -0500, Garrett Wollman wrote: > > As I stated originally, it's impossible to use 'maxsockbuf' value. > > That does not change the fact that an unprivileged user can use up to > `maxsockbuf' bytes of wired kernel memory per socket. That's why the > limit exists. The amount of memory allocated to socket buffer data > structures is not the same as the amount of user data which can be > stored in the socket buffer. Correct me if I wrong, but looks like since rev 1.102 of uipc_socket2.c "something" changed, and should be fixed in some way. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030304043130.B42396>