From: Hangbin Liu <liuhangbin@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, Jay Vosburgh <j.vosburgh@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>, Liang Li <liali@redhat.com>,
Jiri Pirko <jiri@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>
Subject: Re: [PATCHv3 net 2/2] team: reset team's flags when down link is P2P device
Date: Thu, 20 Jul 2023 17:46:04 +0800 [thread overview]
Message-ID: <ZLkCXLsf+K6GLS/6@Laptop-X1> (raw)
In-Reply-To: <ca0a159b39c4e1d192d225e96367c2ff7ffae25e.camel@redhat.com>
On Thu, Jul 20, 2023 at 10:29:19AM +0200, Paolo Abeni wrote:
> > +static void team_ether_setup(struct net_device *dev)
> > +{
> > + unsigned int flags = dev->flags & IFF_UP;
> > +
> > + ether_setup(dev);
> > + dev->flags |= flags;
> > + dev->priv_flags &= ~IFF_TX_SKB_SHARING;
>
> I think we can't do the above. e.g. ether_setup() sets dev->mtu to
> ethernet default, while prior to this patch dev inherited mtu from the
> slaved device. The change may affect the user-space in bad ways.
Hi Paolo,
I don't see the reason why we should inherited a none ethernet dev's mtu
to an ethernet dev (i.e. add a none ethernet dev to team, then delete it and
re-add a ethernet dev to team). I think the dev type has changed, so the
mtu should also be updated.
BTW, after adding the port, team will also set port's mtu to team's mtu.
>
> I think we just need an 'else' branch in the point2point check above,
> restoring the bcast/mcast flags as needed.
Reset the flags is not enough. All the dev header_ops, type, etc are
all need to be reset back, that's why we need to call ether_setup().
Thanks
Hangbin
next prev parent reply other threads:[~2023-07-20 9:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 10:17 [PATCHv3 net 0/2] Fix up dev flags when add P2P down link Hangbin Liu
2023-07-18 10:17 ` [PATCHv3 net 1/2] bonding: reset bond's flags when down link is P2P device Hangbin Liu
2023-07-18 10:17 ` [PATCHv3 net 2/2] team: reset team's " Hangbin Liu
2023-07-20 8:29 ` Paolo Abeni
2023-07-20 9:46 ` Hangbin Liu [this message]
2023-07-20 10:40 ` Paolo Abeni
2023-07-21 3:43 ` Hangbin Liu
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=ZLkCXLsf+K6GLS/6@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=liali@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
/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