Re: LOR route.c:182

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) _at_ /usr/src/sys/net/route.c:182
>  2nd 0xc206537c radix node head (radix node head) _at_ /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