From owner-freebsd-pf@FreeBSD.ORG  Wed Jun 10 13:44:18 2015
Return-Path: <owner-freebsd-pf@FreeBSD.ORG>
Delivered-To: freebsd-pf@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 3E722A65
 for <freebsd-pf@FreeBSD.org>; Wed, 10 Jun 2015 13:44:18 +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 287761955
 for <freebsd-pf@FreeBSD.org>; Wed, 10 Jun 2015 13:44:18 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t5ADiIrC049976
 for <freebsd-pf@FreeBSD.org>; Wed, 10 Jun 2015 13:44:18 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-pf@FreeBSD.org
Subject: [Bug 200330] panic: pf_addr_cmp: unknown address family 0 when scrub
 fragment drop-ovl is used
Date: Wed, 10 Jun 2015 13:44:18 +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-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: commit-hook@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: kristof@freebsd.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-200330-17777-WZwODuokWB@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-200330-17777@https.bugs.freebsd.org/bugzilla/>
References: <bug-200330-17777@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-pf@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Technical discussion and general questions about packet filter
 \(pf\)" <freebsd-pf.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-pf>,
 <mailto:freebsd-pf-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-pf/>
List-Post: <mailto:freebsd-pf@freebsd.org>
List-Help: <mailto:freebsd-pf-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-pf>,
 <mailto:freebsd-pf-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jun 2015 13:44:18 -0000

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

--- Comment #12 from commit-hook@freebsd.org ---
A commit references this bug:

Author: kp
Date: Wed Jun 10 13:44:04 UTC 2015
New revision: 284222
URL: https://svnweb.freebsd.org/changeset/base/284222

Log:
  pf: address family must be set when creating a pf_fragment

  Fix a panic when handling fragmented ip4 packets with 'drop-ovl' set.
  In that scenario we take a different branch in pf_normalize_ip(), taking us
to
  pf_fragcache() (rather than pf_reassemble()). In pf_fragcache() we create a
  pf_fragment, but do not set the address family. This leads to a panic when we
  try to insert that into pf_frag_tree because pf_addr_cmp(), which is used to
  compare the pf_fragments doesn't know what to do if the address family is not
  set.

  Simply ensure that the address family is set correctly (always AF_INET in
this
  path).

  PR:            200330
  Differential Revision:    https://reviews.freebsd.org/D2769
  Approved by:        philip (mentor), gnn (mentor)

Changes:
  head/sys/netpfil/pf/pf_norm.c

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