Re: [PATCH net v2] team: use operstate consistently for linkup

2019-02-22 Thread David Miller
From: George Wilkie Date: Wed, 20 Feb 2019 08:19:11 + > When a port is added to a team, its initial state is derived > from netif_carrier_ok rather than netif_oper_up. > If it is carrier up but operationally down at the time of being > added, the port state.linkup will be set prematurely. > p

Re: [PATCH net v2] team: use operstate consistently for linkup

2019-02-20 Thread Jiri Pirko
Wed, Feb 20, 2019 at 09:19:11AM CET, gwil...@vyatta.att-mail.com wrote: >When a port is added to a team, its initial state is derived >from netif_carrier_ok rather than netif_oper_up. >If it is carrier up but operationally down at the time of being >added, the port state.linkup will be set prematur

[PATCH net v2] team: use operstate consistently for linkup

2019-02-20 Thread George Wilkie
When a port is added to a team, its initial state is derived from netif_carrier_ok rather than netif_oper_up. If it is carrier up but operationally down at the time of being added, the port state.linkup will be set prematurely. port state.linkup should be set consistently using netif_oper_up rather