Date: Tue, 28 Jul 2015 08:00:14 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-pf@FreeBSD.org Subject: [Bug 201932] panic: pf_frag_tree_RB_FIND - dereference to 0xdeadc0dedeadc0de Message-ID: <bug-201932-17777-YyMtEIbkvY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-201932-17777@https.bugs.freebsd.org/bugzilla/> References: <bug-201932-17777@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=201932 Kristof Provost <kp@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-pf@FreeBSD.org |kp@freebsd.org --- Comment #1 from Kristof Provost <kp@freebsd.org> --- Thanks for the report. This is very likely the same issue as bug #201879. A corruption of the fragment cache (a freed element not being removed from the list/tree). I've not yet been able to reproduce this myself, and I can't figure out how it might happen from simple code reading. Knowing that it's related to the v4 path is useful though. -- 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-201932-17777-YyMtEIbkvY>