Kristof Provost 581e697036 Fix panic when adding vtnet interfaces to a bridge ... vtnet interfaces are always in promiscuous mode (at least if the VIRTIO_NET_F_CTRL_RX feature is not negotiated with the host). if_promisc() on a vtnet interface returned ENOTSUP although it has IFF_PROMISC set. This confused the bridge code. Instead we now accept all enable/disable promiscuous commands (and always keep IFF_PROMISC set). There are also two issues with the if_bridge error handling. If if_promisc() fails it uses bridge_delete_member() to clean up. This tries to disable promiscuous mode on the interface. That runs into an assert, because promiscuous mode was never set in the first place. (That's the panic reported in PR 200210.) We can only unset promiscuous mode if the interface actually is promiscuous. This goes against the reference counting done by if_promisc(), but only the first/last if_promic() calls can actually fail, so this is safe. A second issue is a double free of bif. It's already freed by bridge_delete_member(). PR: 200210 Differential Revision: https://reviews.freebsd.org/D2804 Reviewed by: philip (mentor)		2015-06-13 19:39:21 +00:00
..
if_vtnet.c	Fix panic when adding vtnet interfaces to a bridge	2015-06-13 19:39:21 +00:00
if_vtnetvar.h	Add softc flag for when the indirect descriptor feature was negotiated	2015-01-01 02:06:00 +00:00
virtio_net.h	Sync VirtIO net device header file from recent Linux	2013-09-01 04:23:54 +00:00