From owner-freebsd-amd64@freebsd.org  Sat Apr 23 13:52:46 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 BF1AEB12B8E
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Sat, 23 Apr 2016 13:52:46 +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 B05351EF0
 for <freebsd-amd64@FreeBSD.org>; Sat, 23 Apr 2016 13:52:46 +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 u3NDqkpX033434
 for <freebsd-amd64@FreeBSD.org>; Sat, 23 Apr 2016 13:52:46 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 208140] panic: page fault in pf
Date: Sat, 23 Apr 2016 13:52:46 +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: 10.2-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: cc
Message-ID: <bug-208140-6-96XSEekVNn@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-208140-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-208140-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: Sat, 23 Apr 2016 15:23:56 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.21
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: Sat, 23 Apr 2016 13:52:46 -0000

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

Kristof Provost <kp@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kp@freebsd.org

--- Comment #4 from Kristof Provost <kp@freebsd.org> ---
Could you show the contents of (*state)->key[PF_SK_WIRE (0)] and
(*state)->key[PF_SK_STACK (1)] at the time of the panic?

I'm more interested in the state of the pf_state, because the pf_desc is
allocated on the stack in the calling function. It's very unlikely to be a =
bad
pointer here.

My current hypothesis is that you're unlucky enough to have one core in
pf_test_state_udp() trying to use state->key[] while another core is in
pf_state_key_attach().=20

The locking there is rather complicated, so before I dig into that it'd be =
nice
to confirm that one of the PF_SK_WIRE or PF_SK_STACK keys is NULL. (I'd exp=
ect
PF_SK_STACK to be NULL, in fact.)

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