Date: Sat, 12 Sep 2020 12:46:22 +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-Pz5VJpiRmQ@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 #25 from commit-hook@FreeBSD.org --- A commit references this bug: Author: kp Date: Sat Sep 12 12:45:32 UTC 2020 New revision: 365659 URL: https://svnweb.freebsd.org/changeset/base/365659 Log: MFC r365457: net: mitigate vnet / epair cleanup races There's a race where dying vnets move their interfaces back to their orig= inal vnet, and if_epair cleanup (where deleting one interface also deletes the other end of the epair). This is commonly triggered by the pf tests, but also by cleanup of vnet jails. As we've not yet been able to fix the root cause of the issue work around= the panic by not dereferencing a NULL softc in epair_qflush() and by not re-attaching DYING interfaces. This isn't a full fix, but makes a very common panic far less likely. PR: 244703, 238870 Changes: _U stable/12/ stable/12/sys/net/if.c stable/12/sys/net/if_epair.c --=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-Pz5VJpiRmQ>