https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
Bjoern A. Zeeb <b...@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|Affects Only Me |Affects Some People
--- Comment #10 from Bjoern A. Zeeb <b...@freebsd.org> ---
(In reply to Craig Rodrigues from comment #8)
No, it's still used in the same jail.
What seems to happen is:
(a) the bridges get destroyed (all members detached, etc.), the lock gets
destroyed.
(b) the loopback interface in the same jail gets destroyed
(c) the globally registered eventhandler in if_bridge is called for the
interface (lo) disappearing.
(d) we get to the point where we try to acquire the lock which we previously
destroyed.
Either extra checks in bridge_ifdetach() need to be implemented to catch that
case (and I think that's not possible without adding extra bandaid
information), or
proper handling of net cloned interfaces and startup/teardown ordering needs to
be implemented "as a whole".
With all that the CURVET_SET/RESTORE question from comment #1 remains, as to
what happens if bridge_members in the normal case reside in different VNETs
(child jails)?
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
