From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: davem@davemloft.net, vfalico@gmail.com, andy@greyhouse.net,
netdev@vger.kernel.org
Subject: Re: [PATCH] bonding: ban stacked bonding support
Date: Fri, 20 Feb 2015 15:14:00 -0800 [thread overview]
Message-ID: <22754.1424474040@famine> (raw)
In-Reply-To: <20150220222042.GA15595@p183.telecom.by>
Alexey Dobriyan <adobriyan@gmail.com> wrote:
>Does Linux support it at all?
>
>In short: if you add bonding master as a slave, and then release it,
>it will no longer be a IFF_BONDING creating problems like described at
>https://bugzilla.kernel.org/show_bug.cgi?id=89541
>
> echo +bond1 >/sys/class/net/bonding_masters
> echo 1 >/sys/class/net/bond1/bonding/mode
> echo +bond2 >/sys/class/net/bonding_masters
> echo +bond2 >/sys/class/net/bond1/bonding/slaves
> echo -bond2 >/sys/class/net/bond1/bonding/slaves
> echo -bond2 >/sys/class/net/bonding_masters
>
> cat /proc/net/bonding/bond2 # should not exist
> [oops]
>
>Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
I think it's time to disallow stacking like this; it never
really worked quite right as far as I can remember, and I thought it was
disallowed at some point in the past. I don't believe the stacked bonds
function correctly for receive in the current kernel, either, although
I'd have to test it again to confirm that.
The usual case for desiring to stack bonds is an active-backup
pair of LACP / 802.3ad bonds (such as the bugzilla referenced above),
but the 802.3ad mode handles this situation internally, so no stack is
necessary.
>---
>
> drivers/net/bonding/bond_main.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
>--- a/drivers/net/bonding/bond_main.c
>+++ b/drivers/net/bonding/bond_main.c
>@@ -1248,6 +1248,11 @@ int bond_enslave(struct net_device *bond_dev, struct net_device *slave_dev)
> slave_dev->name);
> }
>
>+ if (slave_dev->flags & IFF_MASTER) {
>+ netdev_dbg(bond_dev, "stacked bonding not supported\n");
>+ return -EBUSY;
>+ }
>+
> /* already enslaved */
> if (slave_dev->flags & IFF_SLAVE) {
> netdev_dbg(bond_dev, "Error: Device was already enslaved\n");
Instead of a separate block for IFF_MASTER, the IFF_SLAVE line
could be replaced with something like:
if (netif_is_bond_slave(slave_dev) || netif_is_bond_master(slave_dev)) {
netdev_dbg(bond_dev, "Error: Device is bond slave or master\n");
With that caveat:
Signed-off-by: Jay Vosburgh <jay.vosburgh@canonical.com>
This is probably a good candidate for -stable as well.
-J
---
-Jay Vosburgh, jay.vosburgh@canonical.com
next prev parent reply other threads:[~2015-02-20 23:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 22:20 [PATCH] bonding: ban stacked bonding support Alexey Dobriyan
2015-02-20 23:14 ` Jay Vosburgh [this message]
2015-02-21 2:55 ` Andy Gospodarek
2015-02-21 16:59 ` Jiri Pirko
2015-03-20 17:43 ` Alexey Dobriyan
2015-03-20 17:46 ` [PATCH v2] " Alexey Dobriyan
2015-03-20 20:38 ` David Miller
2015-03-20 21:02 ` Jay Vosburgh
2015-03-20 22:30 ` Jay Vosburgh
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=22754.1424474040@famine \
--to=jay.vosburgh@canonical.com \
--cc=adobriyan@gmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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).