From owner-freebsd-amd64@freebsd.org  Mon Feb 15 09:41:30 2016
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 37FE4AA8C3C
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Mon, 15 Feb 2016 09:41:30 +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 2728E1A39
 for <freebsd-amd64@FreeBSD.org>; Mon, 15 Feb 2016 09:41:30 +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 u1F9fT3x017578
 for <freebsd-amd64@FreeBSD.org>; Mon, 15 Feb 2016 09:41:30 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 207080] pfctl crash when load pf.conf, libc/resolv problem ?
Date: Mon, 15 Feb 2016 09:41:30 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 9.3-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kp@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-pf@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-207080-6-gmOOressHh@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-207080-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-207080-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-Mailman-Approved-At: Mon, 15 Feb 2016 12:08:56 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.20
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: Mon, 15 Feb 2016 09:41:30 -0000

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

--- Comment #4 from Kristof Provost <kp@freebsd.org> ---
Yeah, so this:
=3D=3D17184=3D=3D    by 0x404B46: pfctl_rules (pfctl.c:1486)
=3D=3D17184=3D=3D    by 0x406DA7: main (pfctl.c:2378)
=3D=3D17184=3D=3D  Address 0x6aa8a08 is 56 bytes inside a block of size 64 =
free'd
=3D=3D17184=3D=3D    at 0x4C1E2DC: free (in
/usr/local/lib/valgrind/vgpreload_memcheck-amd64-freebsd.so)
=3D=3D17184=3D=3D    by 0x4210A0: superblock_free (pfctl_optimize.c:1640)
=3D=3D17184=3D=3D    by 0x4233BE: pfctl_optimize_ruleset (pfctl_optimize.c:=
357)
=3D=3D17184=3D=3D    by 0x40453B: pfctl_load_ruleset (pfctl.c:1297)
=3D=3D17184=3D=3D    by 0x404B46: pfctl_rules (pfctl.c:1486)
=3D=3D17184=3D=3D    by 0x406DA7: main (pfctl.c:2378)

Is likely the reason your pfctl segfaults. There's a use after free. It's n=
ot
the direct cause though, that's the kernel rejecting your rules.

Would it be possible to upgrade the machine to stable/10? It looks like the
problem is fixed there.

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