From owner-freebsd-current@FreeBSD.ORG  Thu Oct 30 12:36:30 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 F1EA016A4DE
	for <freebsd-current@freebsd.org>;
	Thu, 30 Oct 2003 12:36:30 -0800 (PST)
Received: from ebb.errno.com (ebb.errno.com [66.127.85.87])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3E3BF43FB1
	for <freebsd-current@freebsd.org>;
	Thu, 30 Oct 2003 12:36:30 -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 h9UKaR0x047778
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Thu, 30 Oct 2003 12:36:29 -0800 (PST)
	(envelope-from sam@errno.com)
From: Sam Leffler <sam@errno.com>
Organization: Errno Consulting
To: othermark <atkin901@yahoo.com>, freebsd-current@freebsd.org
Date: Thu, 30 Oct 2003 12:38:07 -0800
User-Agent: KMail/1.5.3
References: <3FA0BCEB.5020707@mikulas.com> <bnrlci$rhn$1@sea.gmane.org>
In-Reply-To: <bnrlci$rhn$1@sea.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200310301238.07654.sam@errno.com>
Subject: Re: LOR route.c:182
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Oct 2003 20:36:31 -0000

On Thursday 30 October 2003 10:30 am, othermark wrote:
> I'll me too this one..
>
> Another backtrace with a different call sequence (via ipv6), exact same LOR
>
> lock order reversal
>  1st 0xc2177c90 rtentry (rtentry) @ /usr/src/sys/net/route.c:182
>  2nd 0xc206537c radix node head (radix node head) @ /usr/src/sys/net
> route.c:544
> Stack backtrace:
> backtrace(c0841847,c206537c,c08472ff,c08472ff,c0847355) at backtrace+0x17
> witness_lock(c206537c,8,c0847355,220,c0926300) at witness_lock+0x672
> _mtx_lock_flags(c206537c,0,c0847355,220,c8f45868) at _mtx_lock_flags+0xba
> rtrequest1(1,c8f45874,c8f458c8,0,c24376b0) at rtrequest1+0x59
> rtrequest(1,c24376b0,c24376b0,c8f458cc,405) at rtrequest+0x4a
> in6_ifloop_request(1,c2437600,0,c2437600,40) at in6_ifloop_request+0x76
> in6_ifaddloop(c2437600,0,c2437600,0,c8f45a84) at in6_ifaddloop+0x50
> in6_ifinit(c2000000,c2437600,c8f45a2c,1,1be) at in6_ifinit+0x147
> in6_update_ifa(c2000000,c8f45a1c,0,0,20080fe) at in6_update_ifa+0x500
> in6_ifadd(c8f45b34,0,40,0,0) at in6_ifadd+0x22a

I've got fixes for almost all the outstanding LOR's and recursive lock 
problems.  I'm doing more testing before I committing them.

	Sam