From owner-freebsd-current@freebsd.org Fri Mar 25 05:14:54 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A5CFADC5EF for ; Fri, 25 Mar 2016 05:14:54 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward11p.cmail.yandex.net (forward11p.cmail.yandex.net [87.250.241.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4B2951BF2 for ; Fri, 25 Mar 2016 05:14:53 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from web18g.yandex.ru (web18g.yandex.ru [95.108.252.118]) by forward11p.cmail.yandex.net (Yandex) with ESMTP id 3783520E44; Fri, 25 Mar 2016 08:14:36 +0300 (MSK) Received: from web18g.yandex.ru (localhost [127.0.0.1]) by web18g.yandex.ru (Yandex) with ESMTP id 91A8F42A12A0; Fri, 25 Mar 2016 08:14:35 +0300 (MSK) Received: by web18g.yandex.ru with HTTP; Fri, 25 Mar 2016 08:14:33 +0300 From: Alexander V. Chernikov Envelope-From: melifaro@ipfw.ru To: Guy Yur , freebsd-current In-Reply-To: References: null Subject: Re: panic "wlock already held" when changing ipv6 default route MIME-Version: 1.0 Message-Id: <1317681458882873@web18g.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Fri, 25 Mar 2016 08:14:33 +0300 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 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: Fri, 25 Mar 2016 05:14:54 -0000 25.03.2016, 02:11, "Guy Yur" : > Hi, > > When changing the ipv6 default route I get a panic on wlock already held. > Could be related to r293424 lock changes, haven't checked an older version yet. Hi, Yes, there is a problem when the default route next hop is filled in incorrectly, so lookup fails (e.g. matches previous one). Will be fixed soon. Thanks for the report. > > route add -inet6 default fe80::7 > route change -inet6 default fe80::7 > > panic: rw_rlock: wlock already held for rib head lock @ > /usr/src/sys/net/route.c:445 > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0050ee01d0 > vpanic() at vpanic+0x182/frame 0xfffffe0050ee0250 > kassert_panic() at kassert_panic+0x126/frame 0xfffffe0050ee02c0 > __rw_rlock() at __rw_rlock+0xe7/frame 0xfffffe0050ee0360 > rtalloc1_fib() at rtalloc1_fib+0x86/frame 0xfffffe0050ee0420 > ifa_ifwithroute() at ifa_ifwithroute+0x83/frame 0xfffffe0050ee0460 > rt_getifa_fib() at rt_getifa_fib+0xe7/frame 0xfffffe0050ee0480 > rtrequest1_fib() at rtrequest1_fib+0x59c/frame 0xfffffe0050ee0570 > route_output() at route_output+0x653/frame 0xfffffe0050ee07c0 > sosend_generic() at sosend_generic+0x436/frame 0xfffffe0050ee0880 > soo_write() at soo_write+0x42/frame 0xfffffe0050ee08b0 > dofilewrite() at dofilewrite+0x87/frame 0xfffffe0050ee0900 > kern_writev() at kern_writev+0x68/frame 0xfffffe0050ee0950 > sys_write() at sys_write+0x60/frame 0xfffffe0050ee09a0 > amd64_syscall() at amd64_syscall+0x2db/frame 0xfffffe0050ee0ab0 > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe0050ee0ab0 > --- syscall (4, FreeBSD ELF64, sys_write), rip = 0x800977b7ba, rsp = > 0x7fffffffe2d8, rbp = 0x7fffffffeb90 --- > KDB: enter: panic > [ thread pid 644 tid 100054 ] > Stopped at kdb_enter+0x3b: movq $0,kdb_why > > Booted into livecd with snapshot iso in a VirtualBox VM and ran the > commands above. > FreeBSD-11.0-CURRENT-amd64-20160308-r296485-bootonly.iso > > -- Guy > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"