From: Hangbin Liu <liuhangbin@gmail.com>
To: Jay Vosburgh <jay.vosburgh@canonical.com>
Cc: Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andy Gospodarek <andy@greyhouse.net>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
syzbot <syzkaller@googlegroups.com>
Subject: Re: [PATCH net] bonding: stop the device in bond_setup_by_slave()
Date: Sat, 11 Nov 2023 14:34:47 +0800 [thread overview]
Message-ID: <ZU8ghyf+tAUnk7gI@Laptop-X1> (raw)
In-Reply-To: <84246.1699607962@vermin>
On Fri, Nov 10, 2023 at 11:19:22AM +0200, Jay Vosburgh wrote:
> >Do we need also do this if the bond changed to ether device from other dev
> >type? e.g.
> >
> > if (slave_dev->type != ARPHRD_ETHER)
> > bond_setup_by_slave(bond_dev, slave_dev);
> > else
> > bond_ether_setup(bond_dev);
>
> I'm not sure I follow your comment; bond_enslave() already has
> the above logic. If the bond is not ARPHRD_ETHER and an ARPHRD_ETHER
> device is added to the bond, the above will take the bond_ether_setup()
> path, which will call ether_setup() which will set the device to
> ARPHRD_ETHER.
>
> However, my recollection is that the bond device itself should
> be unregistered if the last interface of a non-ARPHRD_ETHER bond is
> removed. This dates back to d90a162a4ee2 ("net/bonding: Destroy bonding
> master when last slave is gone"), but I don't know if the logic still
> works correctly (I've not heard much about IPoIB with bonding in a
> while). The bond cannot be initially created as non-ARPHRD_ETHER; the
> type changes when the first such interface is added to the bond.
Ah, thanks for this info. I just tried and it still works. Which looks
there is no need to close bond dev before bond_ether_setup().
BTW, I tried to set gre0's master to bond0 and change the types. After that,
`ip link del gre0` will return 0 but gre0 is actually not deleted. I have to
remove the gre mode to delete the link. Is that expected?
```
# ip link add bond0 type bond mode 1 miimon 100
# ip link add gre0 type gre
# ip link set gre0 master bond0
# ip link show bond0
21: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/gre 0.0.0.0 brd 0.0.0.0
# ip link del gre0
# echo $?
0
# ip link show gre0
18: gre0@NONE: <NOARP,SLAVE,UP,LOWER_UP> mtu 1500 qdisc noqueue master bond0 state UNKNOWN mode DEFAULT group default qlen 1000
link/gre 0.0.0.0 brd 0.0.0.0
```
Thanks
Hangbin
next prev parent reply other threads:[~2023-11-11 6:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 18:01 [PATCH net] bonding: stop the device in bond_setup_by_slave() Eric Dumazet
2023-11-09 20:26 ` Jay Vosburgh
2023-11-10 3:44 ` Hangbin Liu
2023-11-10 8:38 ` Eric Dumazet
2023-11-11 6:28 ` Hangbin Liu
2023-11-10 9:19 ` Jay Vosburgh
2023-11-11 6:34 ` Hangbin Liu [this message]
2023-11-14 0:43 ` Jay Vosburgh
2023-11-14 1:30 ` Hangbin Liu
2023-11-14 5:00 ` patchwork-bot+netdevbpf
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=ZU8ghyf+tAUnk7gI@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jay.vosburgh@canonical.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller@googlegroups.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