summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorDi Zhu <zhudi21@huawei.com>2021-06-23 06:21:08 +0300
committerDavid S. Miller <davem@davemloft.net>2021-06-23 23:43:44 +0300
commit4d293fe1c69c157c15ac06918a805e5fef036682 (patch)
treebe3ace5762dae19b14a72be3c6dd42647fa1675c /drivers
parent7c2becf7968bda70c457565d42d06f76251edefe (diff)
downloadlinux-4d293fe1c69c157c15ac06918a805e5fef036682.tar.xz
bonding: allow nesting of bonding device
The commit 3c9ef511b9fa ("bonding: avoid adding slave device with IFF_MASTER flag") fix a crash when add slave device with IFF_MASTER, but it rejects the scenario of nested bonding device. As Eric Dumazet described: since there indeed is a usage scenario about nesting bonding, we should not break it. So we add a new judgment condition to allow nesting of bonding device. Fixes: 3c9ef511b9fa ("bonding: avoid adding slave device with IFF_MASTER flag") Suggested-by: Jay Vosburgh <jay.vosburgh@canonical.com> Signed-off-by: Di Zhu <zhudi21@huawei.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/net/bonding/bond_main.c4
1 files changed, 3 insertions, 1 deletions
diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
index 16840c9bc00d..03b1a93d7fea 100644
--- a/drivers/net/bonding/bond_main.c
+++ b/drivers/net/bonding/bond_main.c
@@ -1601,7 +1601,9 @@ int bond_enslave(struct net_device *bond_dev, struct net_device *slave_dev,
int link_reporting;
int res = 0, i;
- if (slave_dev->flags & IFF_MASTER) {
+ if (slave_dev->flags & IFF_MASTER &&
+ !netif_is_bond_master(slave_dev)) {
+ NL_SET_ERR_MSG(extack, "Device with IFF_MASTER cannot be enslaved");
netdev_err(bond_dev,
"Error: Device with IFF_MASTER cannot be enslaved\n");
return -EPERM;