From owner-freebsd-net@freebsd.org  Wed Feb  1 21:45:59 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@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 020D1CCB623
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Wed,  1 Feb 2017 21:45:59 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
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 E5EAF1CC
 for <freebsd-net@FreeBSD.org>; Wed,  1 Feb 2017 21:45:58 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v11LjwfM050616
 for <freebsd-net@FreeBSD.org>; Wed, 1 Feb 2017 21:45:58 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 216304] Adding xn0 to bridge0 causes kernel panic
Date: Wed, 01 Feb 2017 21:45:58 +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-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: commit-hook@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-216304-2472-7apRbS35kU@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-216304-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-216304-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 21:45:59 -0000

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

--- Comment #9 from commit-hook@freebsd.org ---
A commit references this bug:

Author: kp
Date: Wed Feb  1 21:44:50 UTC 2017
New revision: 313066
URL: https://svnweb.freebsd.org/changeset/base/313066

Log:
  MFC 312782

  bridge: Release the bridge lock when calling bridge_set_ifcap()

  This calls ioctl() handlers for the different interfaces in the bridge.
  These handlers expect to get called in an ioctl context where it's safe
  for them to sleep. We may not sleep with the bridge lock held.

  However, we still need to protect the interface list, to ensure it
  doesn't get changed while we iterate over it.
  Use BRIDGE_XLOCK(), which prevents bridge members from being removed.
  Adding bridge members is safe, because it uses LIST_INSERT_HEAD().

  This caused panics when adding xen interfaces to a bridge.

  PR:           216304
  Reviewed by:  ae
  Sponsored by: RootBSD
  Differential Revision:        https://reviews.freebsd.org/D9290

Changes:
_U  stable/10/
  stable/10/sys/net/if_bridge.c
  stable/10/sys/net/if_bridgevar.h

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