Date: Wed, 16 Feb 2000 14:16:22 -0800 From: Jason Evans <jasone@canonware.com> To: Jason Evans <jasone@canonware.com> Cc: Matthew Dillon <dillon@apollo.backplane.com>, current@FreeBSD.org Subject: Re: Heads up, vm.max_proc_mmap sysctl added Message-ID: <20000216141622.E18774@sturm.canonware.com> In-Reply-To: <20000216141339.C18774@sturm.canonware.com>; from jasone@canonware.com on Wed, Feb 16, 2000 at 02:13:39PM -0800 References: <200002162118.NAA54097@apollo.backplane.com> <20000216141339.C18774@sturm.canonware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 16, 2000 at 02:13:39PM -0800, Jason Evans wrote: > On Wed, Feb 16, 2000 at 01:18:13PM -0800, Matthew Dillon wrote: > > This deals with a mmap+fork bomb that can cause the kernel to > > eat all of KVM in vm_map_entry structures. The default limit > > should be set generously enough for people using the current > > FreeBSD threads incarnation (and isn't an issue w/ linux > > threads due to rfork resulting in scaling of the limit for the > > shared address space). > > > > Heads up in case a heavy threads programmer sees something I missed. > > Note that thread stack allocation in libc_r also uses mmap() (one region > per thread), so this applies there as well. Never mind. Matt stated this correctly, and I misread it. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000216141622.E18774>