Date: Wed, 17 Jul 2024 09:52:24 +0000 From: bugzilla-noreply@freebsd.org To: pf@FreeBSD.org Subject: [Bug 279899] pf_unlink_state mutex unlock page fault panic Message-ID: <bug-279899-16861-H3UwCwnVkf@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-279899-16861@https.bugs.freebsd.org/bugzilla/> References: <bug-279899-16861@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=3D279899 --- Comment #13 from Franco Fichtner <franco@opnsense.org> --- Bisecting this is a little tricky due to the random nature but I think it's= the backport of https://cgit.freebsd.org/src/commit/?id=3D2671bde99295d9 which now runs pfsync_drop() which is what happens when you don't use pfsync which didn't happen before as the commit suggests. INVARIANTS appears to trip over: panic: pfsync_drop: st->sync_state =3D=3D q without INVARIANTS it just continues and let's this crash at pf_unlink_stat= e() later on. Maybe it's wrong but I also don't appreciate the lack of enthusiasm looking into fixing regressions on stable branches. At least there is enough information on the table already to do something but I don't see any engagement. Cheers, Franco --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-279899-16861-H3UwCwnVkf>