From owner-freebsd-bugs  Wed Feb 16  0:44:21 2000
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by builder.freebsd.org (Postfix) with ESMTP
	id 77A0F4232; Wed, 16 Feb 2000 00:44:20 -0800 (PST)
Received: (from sheldonh@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id AAA58622;
	Wed, 16 Feb 2000 00:44:52 -0800 (PST)
	(envelope-from sheldonh@FreeBSD.org)
Date: Wed, 16 Feb 2000 00:44:52 -0800 (PST)
From: <sheldonh@FreeBSD.org>
Message-Id: <200002160844.AAA58622@freefall.freebsd.org>
To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org,
	dillon@FreeBSD.org
Subject: Re: kern/16573: extensive fork()+mmap() causes 4.0 kernel to panic()
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: extensive fork()+mmap() causes 4.0 kernel to panic()

Responsible-Changed-From-To: freebsd-bugs->dillon
Responsible-Changed-By: sheldonh
Responsible-Changed-When: Wed Feb 16 00:43:53 PST 2000
Responsible-Changed-Why: 
Matt, is the panic in vm_map_insert() expected behaviour inside an
mmapping fork-bomb?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message