From owner-freebsd-net@freebsd.org  Fri Jul 28 16:10:10 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 5D87FDC94BA
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Fri, 28 Jul 2017 16:10:10 +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 4896D668C3
 for <freebsd-net@FreeBSD.org>; Fri, 28 Jul 2017 16:10:10 +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 v6SGA92C088841
 for <freebsd-net@FreeBSD.org>; Fri, 28 Jul 2017 16:10:10 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 220860] Double loading of the if_bridge module causes panic
Date: Fri, 28 Jul 2017 16:10:10 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 11.0-STABLE
X-Bugzilla-Keywords: crash, needs-qa
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: marieheleneka@gmail.com
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: mfc-stable10? mfc-stable11?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-220860-2472-muDLX1GhBc@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-220860-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-220860-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: Fri, 28 Jul 2017 16:10:10 -0000

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

--- Comment #3 from Marie Helene Kvello-Aune <marieheleneka@gmail.com> ---
I've looked at this problem for about a month and then it kind of rotted on=
 my
shelf because busy IRL.

But here's the underlying problems I found which in combination causes this
issue:
1) Build system installs kernel modules even if they're built into kernel=20
2) boot loader doesn't (successfully) check if module exists in kernel and
loads it regardless, as long as it's instructed to do so.

"kldload" properly checks if the module already exists in the kernel and
correctly refuses to load the module.

I didn't test all boot loaders but the second problem at least happens with=
 the
GPT ZFS loader.

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