From: Jiri Pirko <jiri@resnulli.us>
To: Xin Long <lucien.xin@gmail.com>
Cc: network dev <netdev@vger.kernel.org>, davem@davemloft.net
Subject: Re: [PATCH net] team: move dev_mc_sync after master_upper_dev_link in team_port_add
Date: Mon, 26 Mar 2018 16:38:11 +0200 [thread overview]
Message-ID: <20180326143811.GJ1891@nanopsycho> (raw)
In-Reply-To: <e2412cb1b4863791705ee606755c0a8c82973b20.1521998706.git.lucien.xin@gmail.com>
Sun, Mar 25, 2018 at 07:25:06PM CEST, lucien.xin@gmail.com wrote:
>The same fix as in 'bonding: move dev_mc_sync after master_upper_dev_link
>in bond_enslave' is needed for team driver.
>
>The panic can be reproduced easily:
>
> ip link add team1 type team
> ip link set team1 up
> ip link add link team1 vlan1 type vlan id 80
> ip link set vlan1 master team1
>
>Fixes: cb41c997d444 ("team: team should sync the port's uc/mc addrs when add a port")
>Signed-off-by: Xin Long <lucien.xin@gmail.com>
Acked-by: Jiri Pirko <jiri@mellanox.com>
next prev parent reply other threads:[~2018-03-26 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 17:25 [PATCH net] team: move dev_mc_sync after master_upper_dev_link in team_port_add Xin Long
2018-03-26 14:38 ` Jiri Pirko [this message]
2018-03-26 16:53 ` 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=20180326143811.GJ1891@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.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