From owner-freebsd-current@FreeBSD.ORG Wed Nov 19 15:10:20 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01D0416A4CE for ; Wed, 19 Nov 2003 15:10:19 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id E574E43FCB for ; Wed, 19 Nov 2003 15:10:18 -0800 (PST) (envelope-from sam@errno.com) Received: from 66.127.85.91 ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id hAJNAFHQ036246 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 19 Nov 2003 15:10:17 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: "Bjoern A. Zeeb" , current@freebsd.org Date: Wed, 19 Nov 2003 15:12:38 -0800 User-Agent: KMail/1.5.3 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311191512.38726.sam@errno.com> Subject: Re: list of wellknown LORs ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 23:10:20 -0000 On Wednesday 19 November 2003 02:12 pm, Bjoern A. Zeeb wrote: > Hi, > > is anybody involved in fixing perhaps going to put up a site with all the > wellknown LORs and perhaps a state (like: work in progress (by ...), > ingorable, ...). > > I have seen three the last minutes where at least two seem to be known > when grepping through my mailing lists archives and one of those two > has a promised fix with upcoming chnages... > > wouldn't it be good to have one resource for overall status and may > reduce noice ? > > > ---------------------------------------- > lock order reversal > 1st 0xc3a23090 rtentry (rtentry) @ > HEAD/compile-20031119-1814/sys/net/rtsock.c:389 2nd 0xc396587c radix node > head (radix node head) @ HEAD/compile-20031119-1814/sys/net/route.c:1114 > > STATE: > "go away with forthcoming changes" (sam, current@ 2003-11-xx) > Correct, this and at least one other in the routing table should go away with changes about to be committed. > > ---------------------------------------- > lock order reversal > 1st 0xc3a368f8 inp (inp) @ > HEAD/compile-20031119-1814/sys/netinet/tcp_usrreq.c:363 2nd 0xc063b4ac div > (div) @ HEAD/compile-20031119-1814/sys/netinet/ip_divert.c:238 > > STATE: > known: > http://lists.freebsd.org/pipermail/freebsd-current/2003-August/008743.html > + fix available ? > > > ---------------------------------------- > lock order reversal > 1st 0xc063b580 IPFW dynamic rules (IPFW dynamic rules) @ > HEAD/compile-20031119-1814/sys/netinet/ip_fw2.c:2934 2nd 0xc063b548 IPFW > static rules (IPFW static rules) @ > HEAD/compile-20031119-1814/sys/netinet/ip_fw2.c:1586 Stack backtrace: > backtrace(1,0,ffffffff,c06155f0,c0615618) at backtrace+0x12 > witness_lock(c063b548,8,c05cf951,632,c063b548) at witness_lock+0x534 > _mtx_lock_flags(c063b548,0,c05cf951,632) at _mtx_lock_flags+0x7f > ipfw_chk(c9b4ac0c,0,c9b4abb4,c04ba25c,c0615870) at ipfw_chk+0x28e > ip_output(c2f8f600,0,0,0,0) at ip_output+0x9f3 > send_pkt(c3b1a91c,e2e48f46,1a0e0dd3,2,e) at send_pkt+0x13c > ipfw_tick(0) at ipfw_tick+0xae > softclock(0) at softclock+0x176 > ithread_loop(c2f6d580,c9b4ad48,c2f6d580,c048ab00,0) at ithread_loop+0x12b > fork_exit(c048ab00,c2f6d580,c9b4ad48) at fork_exit+0x90 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xc9b4ad7c, ebp = 0 --- There are part of a set of "middleware" LOR's that also have been waiting on the routing table changes. Once those changes are committed I will resolve them. Sam