lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 19 Feb 2019 17:00:00 +0100
From:   Jiri Pirko <>
To:     George Wilkie <>
Cc:     "David S. Miller" <>,
Subject: Re: [PATCH net] team: use operstate consistently for linkup

Tue, Feb 19, 2019 at 04:57:15PM CET, 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 prematurely.
>port state.linkup should be set consistently using
>netif_oper_up rather than netif_carrier_ok.
>Fixes: f1d22a1e0595 ("team: account for oper state")
>Signed-off-by: George Wilkie <>

Acked-by: Jiri Pirko <>

Powered by blists - more mailing lists