From owner-freebsd-net@freebsd.org  Thu May 26 17:24:45 2016
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 05568B4A807
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Thu, 26 May 2016 17:24:45 +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 E9EAD1247
 for <freebsd-net@FreeBSD.org>; Thu, 26 May 2016 17:24: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 u4QHOipE044662
 for <freebsd-net@FreeBSD.org>; Thu, 26 May 2016 17:24:44 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 201694] 10.2-BETA2 crashing when killing VIMAGE/VNET jails
Date: Thu, 26 May 2016 17:24:44 +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: 10.2-STABLE
X-Bugzilla-Keywords: crash, needs-qa, vimage
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: bz@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: mfc-stable10?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-201694-2472-qjWEfvxXmS@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-201694-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-201694-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.22
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: Thu, 26 May 2016 17:24:45 -0000

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

--- Comment #17 from Bjoern A. Zeeb <bz@FreeBSD.org> ---
Just to confirm:  this is believed to a problem with pf only at this point,
right?

Is it also still true, that this only happens with pf compiled in but not if
loaded as a module?

I have various other problems with pf an VNETs in HEAD to address.  I am not
surprised.

Is there any chance you could test changes on non-10.2 in the future?

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