From nobody@FreeBSD.org  Thu Oct 14 10:51:26 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A2B2F16A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 14 Oct 2004 10:51:26 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8306C43D1D
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 14 Oct 2004 10:51:26 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i9EApQr9072020
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 14 Oct 2004 10:51:26 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i9EApQIu072019;
	Thu, 14 Oct 2004 10:51:26 GMT
	(envelope-from nobody)
Message-Id: <200410141051.i9EApQIu072019@www.freebsd.org>
Date: Thu, 14 Oct 2004 10:51:26 GMT
From: Nikolas Britton <freebsd@nbritton.org>
To: freebsd-gnats-submit@FreeBSD.org
Subject: (Kernel Panic) FreeBSD 5.3 Does not survive fork bombing
X-Send-Pr-Version: www-2.3

>Number:         72680
>Category:       kern
>Synopsis:       (Kernel Panic) FreeBSD 5.3 Does not survive fork bombing
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 14 11:00:38 GMT 2004
>Closed-Date:    Fri Oct 15 05:40:11 GMT 2004
>Last-Modified:  Fri Oct 15 05:40:11 GMT 2004
>Originator:     Nikolas Britton
>Release:        FreeBSD 5.3-BETA7
>Organization:
>Environment:
Stock FreeBSD 5.3-BETA7 ISO i386 Disk1
>Description:
FreeBSD does not survive fork bombing (cannot recover the system) and panics about 15 minutes into the event complaining about swapoff. To me this seems like a regression in system stability because 4.x can easily survive this same attack.
>How-To-Repeat:
Run this in a sh shell     :(){ :|:& };:
>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: das 
State-Changed-When: Thu Oct 14 13:03:29 GMT 2004 
State-Changed-Why:  
This doesn't make sense to me.  How is swapoff(2) related to this 
situation?  Please build a kernel with debug support and provide a 
panic message and a backtrace. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=72680 

From: Nikolas Britton <nbritton23@earthlink.net>
To: freebsd-gnats-submit@FreeBSD.org, freebsd@nbritton.org
Cc:  
Subject: Re: kern/72680: (Kernel Panic) FreeBSD 5.3 Does not survive fork
 bombing
Date: Thu, 14 Oct 2004 22:26:18 -0500

 Sorry to have wasted your time but after 3 hours of fork bombing and 
 trying everthing else under the sun, I could not get FreeBSD to panic 
 with the new debug kernel. I guess it was just a fluke or I was doing 
 the wrong thing at the right time (when it paniced the first time it was 
 in the middle of a portupgrade -arR, X session, etc.). here is a list of 
 the many error messages I receviced (if it helps any):
 
 maxproc limit exceeded
 kern.ipc.maxpipekva exceeded
 swap_pager: out of swap space
 swap_pager_getswapspace
 Pipe call failed: bad file descriptor
 kern.maxfiles limit exceeded
 Can't open /dev/null: Too meny open files in the system
 Connot fork: Resource temporarily unavailable
 ad0: WARNING - READ_DMA interrupt was seen but timeout fired LBA=xxxxxx
 
 Also I take back what I said about freebsd 5.3 being unstable, you guys 
 really know how to build'em, at one time I had the system load (top) for 
 the 1min avg. pegged in the 90s and the 15min. avg. in the 50s - 60s. At 
 the end of my testing I did finally get the system into an unrecoverable 
 state and was forced to reboot it, I was running it with X up and when I 
 try to switch to the console the screen went dead. I blame this one on 
 X. It wasn't a total waste though as I did get to thoroughly burn-in and 
 stress test my new (Used Armada 1750) laptop. So guess this PR is closed 
 unless someone else can crash beastie.
 
State-Changed-From-To: feedback->closed 
State-Changed-By: das 
State-Changed-When: Fri Oct 15 05:39:39 GMT 2004 
State-Changed-Why:  
Closed at submitter's request; cannot reproduce. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=72680 
>Unformatted:
