lists.openwall.net | 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
| ||
|
Date: Sat, 12 Jan 2019 21:13:52 -0800 From: Florian Fainelli <f.fainelli@...il.com> To: Heiner Kallweit <hkallweit1@...il.com>, Andrew Lunn <andrew@...n.ch>, David Miller <davem@...emloft.net> CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, Chris Wilson <chris@...is-wilson.co.uk> Subject: Re: [PATCH net] net: phy: fix too strict check in phy_start_aneg On January 9, 2019 11:34:56 AM PST, Heiner Kallweit <hkallweit1@...il.com> wrote: >When adding checks to detect wrong usage of the phylib API we added >a check to phy_start_aneg() which is too strict. If the phylib >state machine is in state PHY_HALTED we should allow reconfiguring >and restarting aneg, and just don't touch the state. > >Fixes: 2b3e88ea6528 ("net: phy: improve phy state checking") >Reported-by: Chris Wilson <chris@...is-wilson.co.uk> >Signed-off-by: Heiner Kallweit <hkallweit1@...il.com> Reviewed-by: Florian Fainelli <f.fainelli@...il.com> -- Florian
Powered by blists - more mailing lists