Re: setsockopt(RCVBUF) Invalid argument with 2.1.103

Alan Cox (alan@lxorguk.ukuu.org.uk)
Wed, 3 Jun 1998 11:38:14 +0100 (BST)


> I do not plan to change the default {r,w}mem setting but I would like
> to change their max settings. A) it doesn't hurt to allow 200K
> buffers, b) a lot of software actually tries to set this (nfsd is one
> if I remember correctly).

Until Linus wakes up and allows a per user resource management facility and
includes committed physical memory in it (which btw cleans up mlock and fixes
the PTE problems) its not possible. In fact for 2.1.x even the existing
defaults are unsafe and broken. It isnt however a networking problem really
its a resource problem.

I suspect closer to 2.2 Im going to have to post a stream of exploits to this
so that the fixes in the resource code have to be done before 2.2 can be
released.

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu