Date: Fri, 05 Jul 2019 12:11:11 +0000 From: bugzilla-noreply@freebsd.org To: testing@freebsd.org Subject: [Bug 238870] sys.netpfil.pf.names.names and sys.netpfil.pf.synproxy.synproxy cause panic Message-ID: <bug-238870-32464-YnpIHp9wRJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238870-32464@https.bugs.freebsd.org/bugzilla/> References: <bug-238870-32464@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=238870 --- Comment #7 from Kristof Provost <kp@freebsd.org> --- Created attachment 205530 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205530&action=edit ifp_dying.patch A second experimental patch. This solves a different problem, that also manifests during the pf tests. It looks like there's a race, where the epair deletes its ifp while the jail shuts down. The jail shutdown moves the ifp back into its original vnet, while the epair delete is causing it to be deleted. As a result we end up with a freed ifp in V_ifnet, and when we run into it later the box panics. I think this is likely fallout from the epoch-ification, so mmacy@ should take a look at this. -- 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-238870-32464-YnpIHp9wRJ>