Date: Fri, 03 Feb 2023 07:44:26 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 268246] crash and panic using pfsync on 13.1-RELEASE Message-ID: <bug-268246-7501-rRq0Yp3Q8N@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268246-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-268246-7501@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=3D268246 --- Comment #54 from Kristof Provost <kp@freebsd.org> --- (In reply to jjasen from comment #53) I really need to be able to reproduce this, or at least poke at a machine t= hat can trigger this somewhat reliably. Until then we're stuck doing test-kernels with added assertions. I've exten= ded the patch to also check the mbuf when it comes out of the queue again. I'm = kind of hoping it'll look good then, because then we might be looking at a bug in ip_fragment() rather than corruption while it's queued. I've uploaded the patch here, because it's getting a bit unwieldy for the comment field. https://people.freebsd.org/~kp/0001-pfsync-debug-hacks-for-PR268246.patch --=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-268246-7501-rRq0Yp3Q8N>