From owner-freebsd-net@FreeBSD.ORG  Mon Jan 19 15:16:54 2015
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id C2DF857E
 for <freebsd-net@FreeBSD.org>; Mon, 19 Jan 2015 15:16:54 +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 A860BAE0
 for <freebsd-net@FreeBSD.org>; Mon, 19 Jan 2015 15:16:54 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t0JFGstl066799
 for <freebsd-net@FreeBSD.org>; Mon, 19 Jan 2015 15:16:54 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 195859] Reproduceble panic with VIMAGE + if_bridge
Date: Mon, 19 Jan 2015 15:16:54 +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: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: bz@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_severity
Message-ID: <bug-195859-2472-nWYh6QAyZk@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-195859-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-195859-2472@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jan 2015 15:16:54 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859

Bjoern A. Zeeb <bz@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Affects Only Me             |Affects Some People

--- Comment #10 from Bjoern A. Zeeb <bz@FreeBSD.org> ---
(In reply to Craig Rodrigues from comment #8)

No, it's still used in the same jail.

What seems to happen is:
(a) the bridges get destroyed (all members detached, etc.), the lock gets
destroyed.
(b) the loopback interface in the same jail gets destroyed
(c) the globally registered eventhandler in if_bridge is called for the
interface (lo) disappearing.
(d) we get to the point where we try to acquire the lock which we previously
destroyed.

Either extra checks in bridge_ifdetach() need to be implemented to catch that
case (and I think that's not possible without adding extra bandaid
information), or
proper handling of net cloned interfaces and startup/teardown ordering needs to
be implemented "as a whole".

With all that the CURVET_SET/RESTORE question from comment #1 remains, as to
what happens if bridge_members in the normal case reside in different VNETs
(child jails)?

-- 
You are receiving this mail because:
You are the assignee for the bug.