Date: Thu, 18 Jul 2024 13:53:32 +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-J1oJxMUAXP@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 #16 from Zhenlei Huang <zlei@FreeBSD.org> --- (In reply to Franco Fichtner from comment #15) I noticed that days ago but have not tested it yet ... Kristof does not mention this issue in the commit. I can not conclude but I guess this issue persists. Anyway I'll try to figure out what's wrong. I presume https://cgit.freebsd.org/src/commit/?id=3D2671bde99295d9 revealed a= case that pfsync_drop() will not perform good, as before that backport `ifp->if_= bpf` can not be NULL so `pfsync_drop()` below the check is unreachable ... --=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-J1oJxMUAXP>