[Bug 238870] sys.netpfil.pf.names.names and sys.netpfil.pf.synproxy.synproxy cause panic

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Nov 21 15:52:34 UTC 2019


--- Comment #20 from Kristof Provost <kp at freebsd.org> ---
(In reply to Bjoern A. Zeeb from comment #19)
I believe it is related to epair, yes. There are some notes in

My recollection from when I was chasing this is that the problem occurs when a
vnet jail (which contains one or more pair interfaces) is destroyed and
immediately afterwards the epair interface is destroyed (or possibly the other
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).

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-testing mailing list