From: Vlad Yasevich <vyasevich@gmail.com>
To: Kevin Wallace <kevin@pentabarf.net>, netdev@vger.kernel.org
Cc: Michal Kubecek <mkubecek@suse.cz>
Subject: Re: [PATCH v2] macvlan: Support creating macvtaps from macvlans
Date: Tue, 03 Dec 2013 11:17:37 -0500 [thread overview]
Message-ID: <529E0421.2090504@gmail.com> (raw)
In-Reply-To: <1386068122-12039-1-git-send-email-kevin@pentabarf.net>
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@pentabarf.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
next prev parent reply other threads:[~2013-12-03 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 4:13 [PATCH] macvlan: Support creating macvtaps from macvlans Kevin Wallace
2013-12-03 8:24 ` Michal Kubecek
2013-12-03 9:58 ` Kevin Wallace
2013-12-03 10:55 ` [PATCH v2] " Kevin Wallace
2013-12-03 16:17 ` Vlad Yasevich [this message]
2013-12-03 17:46 ` Kevin Wallace
2013-12-03 19:47 ` Michal Kubecek
2013-12-04 13:59 ` Vlad Yasevich
2013-12-04 14:23 ` Michal Kubecek
2013-12-04 14:57 ` Vlad Yasevich
2013-12-06 0:59 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=529E0421.2090504@gmail.com \
--to=vyasevich@gmail.com \
--cc=kevin@pentabarf.net \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).