[Bug 279899] pf_unlink_state mutex unlock page fault panic

From: <bugzilla-noreply_at_freebsd.org>
Date: Sun, 23 Jun 2024 08:54:35 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279899

--- Comment #1 from Kristof Provost <kp@freebsd.org> ---
(In reply to Daniel Ponte from comment #0)
All right, first off: did you mean eff27c3872300 rather than ff27c3872300?

Secondly, what is your setup? Post your ruleset and network configuration. Are
you using pfsync, pflog, ....?

Lastly, build an INVARIANTS kernel and see what assertions you hit.

The panic seems to show us locking a hashrow that the state is not in, which
explains the panic on mutex unlock (because we're unlocking a different mutex
from the one we locked), but there's no obvious way for that to happen. That
would be why it's important to provide setup details!

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