[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 11 Nov 2009 16:36:06 +0100
From: Patrick McHardy <kaber@...sh.net>
To: Patrick Mullaney <pmullaney@...ell.com>
CC: alacrityvm-devel@...ts.sourceforge.net,
linux-kernel@...r.kernel.org, arnd@...db.de,
bridge@...ts.linux-foundation.org, evb@...oogroups.com,
netdev@...r.kernel.org
Subject: Re: [PATCH 4/4] venet-macvlan: add new driver to connect a venet
to a macvlan netdevice
Patrick Mullaney wrote:
> This driver implements a macvlan device as a venet device that can
> be connected to vbus. Since it is a macvlan device, it provides
> a more direct path to the underlying adapter by avoiding the
> bridge.
> --- /dev/null
> +++ b/kernel/vbus/devices/venet/macvlan.c
> ...
> +struct venetmacv {
> + struct macvlan_dev mdev;
> + unsigned char ll_ifname[IFNAMSIZ];
> + struct venetdev dev;
> + const struct net_device_ops *macvlan_netdev_ops;
> +};
macvlan might destroy the device below you when the underlying
device is unregistered. You need to handle this by releasing
the venetmacv device. Check out the NETDEV_UNREGISTER case in
macvlan_device_event().
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists