Re: [PATCH net] team: move dev_mc_sync after master_upper_dev_link in team_port_add

2018-03-26 Thread David Miller
From: Xin Long Date: Mon, 26 Mar 2018 01:25:06 +0800 > 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

Re: [PATCH net] team: move dev_mc_sync after master_upper_dev_link in team_port_add

2018-03-26 Thread Jiri Pirko
Sun, Mar 25, 2018 at 07:25:06PM CEST, lucien@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

[PATCH net] team: move dev_mc_sync after master_upper_dev_link in team_port_add

2018-03-25 Thread Xin Long
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: