From owner-freebsd-ipfw@freebsd.org  Fri Sep 30 03:42:13 2016
Return-Path: <owner-freebsd-ipfw@freebsd.org>
Delivered-To: freebsd-ipfw@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 7A54DC03932
 for <freebsd-ipfw@mailman.ysv.freebsd.org>;
 Fri, 30 Sep 2016 03:42:13 +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 69C8093B
 for <freebsd-ipfw@FreeBSD.org>; Fri, 30 Sep 2016 03:42:13 +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 u8U3gDO7067481
 for <freebsd-ipfw@FreeBSD.org>; Fri, 30 Sep 2016 03:42:13 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ipfw@FreeBSD.org
Subject: [Bug 212649] ipfw(8): Referencing a table in the ruleset causes ipfw
 list/show to crash with SIGSEGV.
Date: Fri, 30 Sep 2016 03:42:13 +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-RC1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: ae@FreeBSD.org
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ipfw@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-212649-7515-tEYqQIeDrE@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-212649-7515@https.bugs.freebsd.org/bugzilla/>
References: <bug-212649-7515@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-ipfw@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: IPFW Technical Discussions <freebsd-ipfw.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ipfw>,
 <mailto:freebsd-ipfw-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ipfw/>
List-Post: <mailto:freebsd-ipfw@freebsd.org>
List-Help: <mailto:freebsd-ipfw-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ipfw>,
 <mailto:freebsd-ipfw-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Sep 2016 03:42:13 -0000

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

--- Comment #8 from Andrey V. Elsukov <ae@FreeBSD.org> ---
(In reply to Jan Bramkamp from comment #6)
> I applied the patch from #212649 to 11.0-RC2 and it fixed the problem. Is
> there any chance for the patch to be included in 11.0-RELEASE?

No, it wont be in 11.0-RELEASE. Probably in some errata after release.

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