From owner-freebsd-current@FreeBSD.ORG Tue Oct 28 12:58:41 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 0AF3116A4CE for ; Tue, 28 Oct 2003 12:58:41 -0800 (PST) Received: from demos.su (mx.demos.su [194.87.0.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5186743FDF for ; Tue, 28 Oct 2003 12:58:39 -0800 (PST) (envelope-from mitya@fling-wing.demos.su) Received: from [194.87.5.69] (HELO fling-wing.demos.su) by demos.su (CommuniGate Pro SMTP 4.1.5/D1) with ESMTP-TLS id 121505636 for current@freebsd.org; Tue, 28 Oct 2003 23:58:37 +0300 Received: from fling-wing.demos.su (localhost [127.0.0.1]) by fling-wing.demos.su (8.12.9/8.12.6) with ESMTP id h9SKwblI072527 for ; Tue, 28 Oct 2003 23:58:37 +0300 (MSK) (envelope-from mitya@fling-wing.demos.su) Received: (from mitya@localhost) by fling-wing.demos.su (8.12.9/8.12.6/Submit) id h9SKwaWj072526 for current@freebsd.org; Tue, 28 Oct 2003 23:58:36 +0300 (MSK) Date: Tue, 28 Oct 2003 23:58:36 +0300 From: Dmitry Sivachenko To: current@freebsd.org Message-ID: <20031028205836.GA72290@fling-wing.demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline WWW-Home-Page: http://mitya.pp.ru/ X-PGP-Key: http://mitya.pp.ru/mitya.asc User-Agent: Mutt/1.5.4i Subject: LOR 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: Tue, 28 Oct 2003 20:58:41 -0000 Hello! When I establish a dialup link with my ISP using ppp(8), I get the following LOR (very recent -current): lock order reversal 1st 0xc47ab790 rtentry (rtentry) @ /usr/src/sys/net/rtsock.c:388 2nd 0xc442367c radix node head (radix node head) @ /usr/src/sys/net/route.c:133 Stack backtrace: backtrace(c0654bae,c442367c,c065a582,c065a582,c065a5d8) at backtrace+0x17 witness_lock(c442367c,8,c065a5d8,85,246) at witness_lock+0x672 _mtx_lock_flags(c442367c,0,c065a5d8,85,117) at _mtx_lock_flags+0xba rtalloc1(c478de6c,1,10000,3d7,ddb62b44) at rtalloc1+0x79 rt_setgate(c47ab700,c44f1280,c478de6c,184,0) at rt_setgate+0x268 route_output(c1929b00,c4581100,7c,c1929b00,1f84) at route_output+0x62e raw_usend(c4581100,0,c1929b00,0,0) at raw_usend+0x73 rts_send(c4581100,0,c1929b00,0,0) at rts_send+0x35 sosend(c4581100,0,ddb62c7c,c1929b00,0) at sosend+0x44d soo_write(c4504088,ddb62c7c,c478df00,0,c4783ab0) at soo_write+0x70 dofilewrite(c4783ab0,c4504088,3,bfbfec40,7c) at dofilewrite+0xf8 write(c4783ab0,ddb62d10,c066536b,3ed,3) at write+0x6e syscall(2f,2f,2f,3,3) at syscall+0x2c0 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (4), eip = 0x2827b35f, esp = 0xbfbfebfc, ebp = 0xbfbfec28 --- This LOR appeared after massive network stack locking changes by sam@ (but I am not 100% sure that they cause it).