From owner-freebsd-net@FreeBSD.ORG Tue Mar 31 17:35:25 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 67A9ED7E for ; Tue, 31 Mar 2015 17:35:25 +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 4D19B8CE for ; Tue, 31 Mar 2015 17:35:25 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2VHZPop014466 for ; Tue, 31 Mar 2015 17:35:25 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: Tue, 31 Mar 2015 17:35:25 +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: hiren@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: 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: Tue, 31 Mar 2015 17:35:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=171711 --- Comment #4 from Hiren Panchasara --- (In reply to dblais from comment #2) I cannot look into this right now but noticed that what you are reporting looks different than the original post. That seems double free and what you are seeing is locking issue in bpf. I don't know the code very well but that's my understanding. 1 more suggestion, if you have many servers with the exact same panic, what is the frequency of the panics? Can you provide any more info? It'd be really helpful if you can run -current or stable10/release10 on one of those machines as those branches are actively being worked on and there are higher chances that what you are seeing _might_ have been fixed there. my 2 c. -- You are receiving this mail because: You are the assignee for the bug.