netdev - Re: [PATCH v2] macvlan: Support creating macvtaps from macvlans

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 03 Dec 2013 11:17:37 -0500
From:	Vlad Yasevich <vyasevich@...il.com>
To:	Kevin Wallace <kevin@...tabarf.net>, netdev@...r.kernel.org
CC:	Michal Kubecek <mkubecek@...e.cz>
Subject: Re: [PATCH v2] macvlan: Support creating macvtaps from macvlans

On 12/03/2013 05:55 AM, Kevin Wallace wrote:
> When running in a network namespace whose only link to the outside
> world is a macvlan device, not being able to create a macvtap off of
> it is a real pain.
> 
> So modify macvtap creation to automatically forward a creation of a
> macvtap on a macvlan to become a creation of a macvtap on the
> underlying network device, just like is currently done with
> macvlan-on-macvlan devices.
> 
> v2: Use netif_is_macvlan and macvlan_dev_real_dev helpers to make it
>     more clear what we're doing.
> 
> Signed-off-by: Kevin Wallace <kevin@...tabarf.net>
> ---
>  drivers/net/macvlan.c | 8 +++-----
>  1 file changed, 3 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/net/macvlan.c b/drivers/net/macvlan.c
> index acf9379..cfb9157 100644
> --- a/drivers/net/macvlan.c
> +++ b/drivers/net/macvlan.c
> @@ -820,13 +820,11 @@ int macvlan_common_newlink(struct net *src_net, struct net_device *dev,
>  	if (lowerdev == NULL)
>  		return -ENODEV;
>  
> -	/* When creating macvlans on top of other macvlans - use
> +	/* When creating macvlans or macvtaps on top of other macvlans - use
>  	 * the real device as the lowerdev.
>  	 */
> -	if (lowerdev->rtnl_link_ops == dev->rtnl_link_ops) {
> -		struct macvlan_dev *lowervlan = netdev_priv(lowerdev);
> -		lowerdev = lowervlan->lowerdev;
> -	}
> +	if (netif_is_macvlan(lowerdev))
> +		lowerdev = macvlan_dev_real_dev(lowerdev);
>  
>  	if (!tb[IFLA_MTU])
>  		dev->mtu = lowerdev->mtu;
> 

the other question is should this be done in a loop?  What happens if
you have nested namespaces?

-vlad
--
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