From owner-freebsd-net@FreeBSD.ORG Wed Apr 1 06:19:41 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 93C4BC3E for ; Wed, 1 Apr 2015 06:19:41 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 799CD6CB for ; Wed, 1 Apr 2015 06:19:41 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t316Je3e050799 for ; Wed, 1 Apr 2015 06:19:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 171711] [dummynet] [panic] Kernel panic in dummynet Date: Wed, 01 Apr 2015 06:19:41 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 8.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ae@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 06:19:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=171711 Andrey V. Elsukov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ae@FreeBSD.org --- Comment #7 from Andrey V. Elsukov --- (In reply to dblais from comment #2) > #6 0xffffffff80cdbd13 in calltrap () > at /usr/src/sys/amd64/amd64/exception.S:232 > #7 0xffffffff8090adb0 in _rw_rlock (rw=0xfffffe013aade5a8, file=0x0, > line=485069968) at /usr/src/sys/kern/kern_rwlock.c:382 > #8 0xffffffff809c5959 in bpf_mtap2 (bp=0xfffffe013aade580, > data=0xffffff88826429bc, dlen=4, m=0xfffffe0300f46700) > at /usr/src/sys/net/bpf.c:2197 > #9 0xffffffff8188e11a in ng_iface_bpftap (ifp=, m=0x0, > family=144 '\220') > at /usr/src/sys/modules/netgraph/iface/../../../netgraph/ng_iface.c:444 > #10 0xffffffff8188eb11 in ng_iface_output (ifp=0xfffffe014566a000, > m=0xfffffe0300f46700, dst=0xffffff8882642aac, ro=) > at /usr/src/sys/modules/netgraph/iface/../../../netgraph/ng_iface.c:394 This panic looks different. Probably an interface has gone away and BPF's interface departure handler already destroyed bif_lock. -- You are receiving this mail because: You are the assignee for the bug.