Date: Thu, 18 Jul 2024 06:05:35 +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-U2liZoRQaI@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 #15 from Franco Fichtner <franco@opnsense.org> --- Thanks for the response. So it looks like https://cgit.freebsd.org/src/commit/?id=3De99c76951e1 just appeared on stab= le/14 and a mention of 5f75cd390a67 would have been quite helpful a couple of days ago, or would it not? That being said the author provided no context here since at least 3 weeks = and commits are no longer annotated for having been voiced in the bug tracker. = So my guess is as good as anyone's. This pattern has been repeating a number of times the last half a year at l= east so I'd really appreciate if we could bash reporters less and communicate technicalities more especially when stable branches are involved? --=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-U2liZoRQaI>