From owner-freebsd-amd64@freebsd.org  Fri Jan 20 21:47:44 2017
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@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 CD251CBAC4F
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Fri, 20 Jan 2017 21:47:44 +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 BD29B116F
 for <freebsd-amd64@FreeBSD.org>; Fri, 20 Jan 2017 21:47:44 +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 v0KLli9W092646
 for <freebsd-amd64@FreeBSD.org>; Fri, 20 Jan 2017 21:47:44 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 216304] Adding xn0 to bridge0 causes kernel panic
Date: Fri, 20 Jan 2017 21:47:44 +0000
X-Bugzilla-Reason: CC
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: kp@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-216304-6-hbTJAd4RfX@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-216304-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-216304-6@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-amd64@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2017 21:47:44 -0000

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

Kristof Provost <kp@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kp@freebsd.org

--- Comment #1 from Kristof Provost <kp@freebsd.org> ---
Tests with WITNESS show:

xn0: performing interface reset due to feature change
uma_zalloc_arg: zone "64" with the following non-sleepable locks held:
exclusive sleep mutex if_bridge (if_bridge) r =3D 0 (0xfffff80003f0aa18) lo=
cked @
/usr/home/rootbsd/freebsd/sys/modules/if_bridge/../../net/if_bridge.c:826
stack backtrace:
#0 0xffffffff80a66720 at witness_debugger+0x70
#1 0xffffffff80a679c7 at witness_warn+0x3d7
#2 0xffffffff80cb00bb at uma_zalloc_arg+0x3b
#3 0xffffffff809f328c at malloc+0xfc
#4 0xffffffff80a57c45 at sbuf_new+0x95
#5 0xffffffff808eea18 at xs_rm+0x28
#6 0xffffffff808eb411 at xn_ioctl+0x211
#7 0xffffffff8221d4b3 at bridge_ioctl_add+0x4b3
#8 0xffffffff8221ef8f at bridge_ioctl+0x29f
#9 0xffffffff80ae577a at ifioctl+0x104a
#10 0xffffffff80a6ab64 at kern_ioctl+0x214
#11 0xffffffff80a6a8e1 at sys_ioctl+0x171
#12 0xffffffff80e35fd4 at amd64_syscall+0x314
#13 0xffffffff80e1c1ab at Xfast_syscall+0xfb

--=20
You are receiving this mail because:
You are on the CC list for the bug.=