Thread (1 message) 1 message, 1 author, 2016-10-14

Re: [PATCH net-next 00/11] net: Fix netdev adjacency tracking

From: David Miller <hidden>
Date: 2016-10-14 14:17:30
Also in: intel-wired-lan, linux-rdma

From: David Ahern <redacted>
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help