netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Veaceslav Falico <vfalico@redhat.com>
To: Vlad Yasevich <vyasevic@redhat.com>
Cc: Jay Vosburgh <jay.vosburgh@canonical.com>,
	netdev@vger.kernel.org, Andy Gospodarek <andy@greyhouse.net>,
	Ding Tianhong <dingtianhong@huawei.com>,
	Patric McHardy <kaber@trash.net>
Subject: Re: [PATCH v2 net] bonding: Fix stacked device detection in arp monitoring
Date: Wed, 7 May 2014 20:11:00 +0200	[thread overview]
Message-ID: <20140507181100.GU6295@redhat.com> (raw)
In-Reply-To: <20140507174910.GT6295@redhat.com>

On Wed, May 07, 2014 at 07:49:10PM +0200, Veaceslav Falico wrote:
>On Wed, May 07, 2014 at 01:08:09PM -0400, Vlad Yasevich wrote:
>...snip...
>>Yes.  I verified that it works.  The reason is that we are traversing
>>the all_adj_list.upper list which contains all of the upper devices at
>>each level.  So, at vlan100 level, we will see vlan200 and all will be
>>well.
>
>Hrm, two scenarios, with the following config:
>
>bond0 -> whatever1 -> vlan1 -> whatever2 -> vlan2 -> whatever3_IP
>
>end == whatever3_IP
>
...snip...
>
>So, the end patch (not compiled, not tested...) would look something like
>(only the bond_check_path() is changed and copied here, everything else
>remains the same):
>
>+       bool upper_found = false;
>+
>+       netdev_for_each_all_upper_dev_rcu(start, upper, iter) {
>+               if (upper == end)
>+                       upper_found = true;
>+
>+               if (idx < 2 && is_vlan_dev(upper) &&
>+                   bond_check_path(upper, end, tag, idx+1)) {
>+                       tag[idx].vlan_proto = vlan_dev_vlan_proto(upper);
>+                       tag[idx].vlan_id = vlan_dev_vlan_id(upper);
>+                       return true;

Actually, screw that, we might find here the vlan2 first and end up with
only 1 vlan (vlan2, skipping vlan1).

The way to fix this might be to get the most "lengthy" path of vlans, as
in:

+ * Return the maximum length of stacked vlans + device found, 0 if the end
+ * device is not found.
+ */
+static int bond_check_path(struct net_device *start, struct net_device *end,
+                          struct bond_vlan_tag *tag, int idx)
+{
+       struct net_device *upper;
+       struct list_head  *iter;
+       int length, max_length = 0;
+
+       netdev_for_each_all_upper_dev_rcu(start, upper, iter) {
+               if (upper == end && !max_length)
+                       max_length = 1;
+
+               if (idx < 2 && is_vlan_dev(upper)) {
+                       length = bond_check_path(upper, end, tag, idx + 1);
+
+                       if (max_length < length + 1) {
+                               tag[idx].vlan_proto = vlan_dev_vlan_proto(upper);
+                               tag[idx].vlan_id = vlan_dev_vlan_id(upper);
+                               max_length = length + 1;
+                       }
+               }
+       }
+       return max_length;
+}

Hope that helps.

>+               }
>+       }
>+       return upper_found;
...snip...

  reply	other threads:[~2014-05-07 18:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 13:47 [PATCH v2 net] bonding: Fix stacked device detection in arp monitoring Vlad Yasevich
2014-05-07 16:43 ` Jay Vosburgh
2014-05-07 17:08   ` Vlad Yasevich
2014-05-07 17:49     ` Veaceslav Falico
2014-05-07 18:11       ` Veaceslav Falico [this message]
2014-05-07 18:47         ` Vlad Yasevich
2014-05-07 18:59           ` Veaceslav Falico
2014-05-07 19:40             ` Jay Vosburgh
2014-05-07 20:10             ` Veaceslav Falico
2014-05-08  4:25               ` Ding Tianhong

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=20140507181100.GU6295@redhat.com \
    --to=vfalico@redhat.com \
    --cc=andy@greyhouse.net \
    --cc=dingtianhong@huawei.com \
    --cc=jay.vosburgh@canonical.com \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=vyasevic@redhat.com \
    /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).