[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20161014.101730.404820561372500741.davem@davemloft.net>
Date: Fri, 14 Oct 2016 10:17:30 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: dsa@...ulusnetworks.com
Cc: jiri@...lanox.com, netdev@...r.kernel.org, dledford@...hat.com,
sean.hefty@...el.com, hal.rosenstock@...il.com,
linux-rdma@...r.kernel.org, j.vosburgh@...il.com,
vfalico@...il.com, andy@...yhouse.net, jeffrey.t.kirsher@...el.com,
intel-wired-lan@...ts.osuosl.org
Subject: Re: [PATCH net-next 00/11] net: Fix netdev adjacency tracking
From: David Ahern <dsa@...ulusnetworks.com>
Date: Wed, 12 Oct 2016 13:51:48 -0700
> The netdev adjacency tracking is failing to create proper dependencies
> for some topologies. For example this topology
>
> +--------+
> | myvrf |
> +--------+
> | |
> | +---------+
> | | macvlan |
> | +---------+
> | |
> +----------+
> | bridge |
> +----------+
> |
> +--------+
> | bond0 |
> +--------+
> |
> +--------+
> | eth3 |
> +--------+
>
> hits 1 of 2 problems depending on the order of enslavement. The base set of
> commands for both cases:
>
> ip link add bond1 type bond
> ip link set bond1 up
Your diagram uses the device name "bond0" but all of your command examples
use "bond1". Please fix this up, thanks.
Powered by blists - more mailing lists