Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 23 Apr 2016 13:52:46 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-amd64@FreeBSD.org
Subject:   [Bug 208140] panic: page fault in pf
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/>

next in thread | previous in thread | raw e-mail | index | archive | help
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.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-208140-6-96XSEekVNn>