Date: Thu, 21 Nov 2019 15:52:33 +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-jwUTKyCB9U@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=3D238870 --- Comment #20 from Kristof Provost <kp@freebsd.org> --- (In reply to Bjoern A. Zeeb from comment #19) I believe it is related to epair, yes. There are some notes in https://reviews.freebsd.org/D20868 My recollection from when I was chasing this is that the problem occurs whe= n a vnet jail (which contains one or more pair interfaces) is destroyed and immediately afterwards the epair interface is destroyed (or possibly the ot= her way around). Destroying the vnet jail moves the epair interface back into the host, but because it's also being destroyed at the same time we end up moving an ifp = into the host which will be freed afterwards. A freed ifp in the host's list of interfaces is obviously a panic waiting to happen. I'm not 100% clear on the exact order of operations here, but I am fully convinced that it's related to interfaces being moved due to a vnet destroy, and epairs destroying two interfaces at a time (i.e. a and b). --=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-238870-32464-jwUTKyCB9U>