From owner-freebsd-current Wed Feb 16 14:16:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 9E2D337B505 for ; Wed, 16 Feb 2000 14:16:47 -0800 (PST) (envelope-from jasone@canonware.com) Received: from canonware.com (canonware.com [207.20.242.18]) by builder.freebsd.org (Postfix) with SMTP id 7BDC3132D6 for ; Wed, 16 Feb 2000 14:16:09 -0800 (PST) Received: (qmail 21775 invoked by uid 1001); 16 Feb 2000 22:16:22 -0000 Date: Wed, 16 Feb 2000 14:16:22 -0800 From: Jason Evans To: Jason Evans Cc: Matthew Dillon , current@FreeBSD.org Subject: Re: Heads up, vm.max_proc_mmap sysctl added Message-ID: <20000216141622.E18774@sturm.canonware.com> References: <200002162118.NAA54097@apollo.backplane.com> <20000216141339.C18774@sturm.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000216141339.C18774@sturm.canonware.com>; from jasone@canonware.com on Wed, Feb 16, 2000 at 02:13:39PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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