From: Michal Kubecek <mkubecek@suse.cz>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Jay Vosburgh <jay.vosburgh@canonical.com>,
Tom Gundersen <teg@jklm.no>, netdev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
vfalico@gmail.com, andy@greyhouse.net
Subject: Re: [patch net-next] bonding: allow to add vlans on top of empty bond
Date: Wed, 2 Jul 2014 11:05:17 +0200 [thread overview]
Message-ID: <20140702090517.GA5440@unicorn.suse.cz> (raw)
In-Reply-To: <20140702084652.GA3015@minipsycho.orion>
On Wed, Jul 02, 2014 at 10:46:52AM +0200, Jiri Pirko wrote:
> Fri, Jun 27, 2014 at 06:08:50PM CEST, jay.vosburgh@canonical.com wrote:
> >
> > if (!bond_has_slaves(bond)) {
> > bond_set_carrier(bond);
> > eth_hw_addr_random(bond_dev);
> >
> > if (vlan_uses_dev(bond_dev)) {
> > pr_warn("%s: Warning: clearing HW address of %s while it still has VLANs\n",
> > bond_dev->name, bond_dev->name);
> > pr_warn("%s: When re-adding slaves, make sure the bond's HW address matches its VLANs\n",
> > bond_dev->name);
> > }
> > }
> >
> > This warning may not be useful any longer, since the MAC should
> >update correctly without user action when re-adding the first slave.
>
> I just checked. The vlan dev holds its addr. So when new slave is added,
> bond addr is changed to it, but vlan addr remains the same. So the
> second warning still stands.
Is it a problem? Since we have proper uc_list propagation, vlan should
work even if its address doesn't match the bond.
Michal Kubecek
next prev parent reply other threads:[~2014-07-02 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 14:13 [patch net-next] bonding: allow to add vlans on top of empty bond Jiri Pirko
2014-06-27 15:27 ` Tom Gundersen
2014-06-27 16:08 ` Jay Vosburgh
2014-07-02 8:46 ` Jiri Pirko
2014-07-02 9:05 ` Michal Kubecek [this message]
2014-07-02 9:13 ` Jiri Pirko
2014-06-28 7:30 ` Veaceslav Falico
2014-06-28 7:49 ` Jiri Pirko
2014-07-02 1:58 ` 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=20140702090517.GA5440@unicorn.suse.cz \
--to=mkubecek@suse.cz \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=jay.vosburgh@canonical.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=teg@jklm.no \
--cc=vfalico@gmail.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).