From avatar@ksue.edu.ua  Fri Mar  7 00:21:36 2003
Return-Path: <avatar@ksue.edu.ua>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EB03237B401
	for <FreeBSD-gnats-submit@freebsd.org>; Fri,  7 Mar 2003 00:21:36 -0800 (PST)
Received: from ksue.edu.ua (ksue.kharkov.ukrtel.net [195.5.57.77])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0549A43FBD
	for <FreeBSD-gnats-submit@freebsd.org>; Fri,  7 Mar 2003 00:21:33 -0800 (PST)
	(envelope-from avatar@ksue.edu.ua)
Received: (from root@localhost)
	by ksue.edu.ua (8.11.6/8.11.6) id h278MHi52393;
	Fri, 7 Mar 2003 10:22:17 +0200 (EET)
	(envelope-from avatar)
Message-Id: <200303070822.h278MHi52393@ksue.edu.ua>
Date: Fri, 7 Mar 2003 10:22:17 +0200 (EET)
From: hw <hw@ksue.edu.ua>
Reply-To: hw <hw@ksue.edu.ua>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: kernel crashes when ipfw configured with multiply pipes
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         48995
>Category:       kern
>Synopsis:       kernel crashes when ipfw configured with multiply pipes
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Mar 07 00:30:10 PST 2003
>Closed-Date:    Fri Mar 07 01:28:17 PST 2003
>Last-Modified:  Fri Mar 07 01:28:17 PST 2003
>Originator:     hw
>Release:        from FreeBSD 4.4-RELEASE i386 upto FreeBSD 4.7-RELEASE i386
>Organization:
Kharkov State University of Economics
>Environment:
System:
 FreeBSD ksue.edu.ua 4.4-RELEASE FreeBSD 4.4-RELEASE #0: Fri Aug 16 13:29:53 EEST 2002 root@mirinda.local:/usr/src/sys/compile/MIRINDA i386


>Description:
when ipfw configured that packet passes multiply pipes
at once kernel hangs almost on all spectrum of computers and FreeBSD
versions I seen. Crash behaviour depends upon network load and with
big amount of pipes can be achieved with sending one ip/icmp packet.
Regulating amount of pipes used one can crash network activity only
(computer itself will work normally using non-network software).

This piece of /etc/messages is only from one of crashes....
in other circumstances kernel was even unable to record
anything... even unable to reboot.

Fatal trap 10: trace trap while in kernel mode
instruction pointer    = 0x8:0xc013efbd
stack pointer          = 0x10:0xc9947ce4
frame pointer          = 0x10:0xc9947cfc
code segment           = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags       = trace trap, IOPL = 0
current process                = 34772 (perl)
interrupt mask         = net tty
trap number            = 10
panic: trace trap

>How-To-Repeat:
ipfw pipe 1 config
ipfw add 1 pipe 1 all from any to any
ipfw add 1 pipe 1 all from any to any
ipfw add 1 pipe 1 all from any to any
ipfw add 1 pipe 1 all from any to any
ipfw add 1 pipe 1 all from any to any
ipfw add 1 pipe 1 all from any to any
ipfw add 1 pipe 1 all from any to any
ipfw add 1 pipe 1 all from any to any
ipfw add 1 pipe 1 all from any to any
............at your wish.............

>Fix:
Sorry, don't know solution... anyway, queue rules of ipfw works queer
I was unable to implement WF2Q policy using them and code snippet above
was an attempt to solve queues queerness.

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: maxim 
State-Changed-When: Fri Mar 7 01:26:44 PST 2003 
State-Changed-Why:  
Duplicate of kern/37573 and several other PRs. I am working on a fix. 

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