netdev - Re: [drivers/net/phy/sfp] intermittent failure in state machine checks

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <513d6fe7-65b2-733b-1d17-b3a40b8161cf@gmx.net>
Date:   Thu, 9 Jan 2020 15:03:24 +0000
From:   ѽ҉ᶬḳ℠ <vtol@....net>
To:     Andrew Lunn <andrew@...n.ch>,
        Russell King <rmk+kernel@....linux.org.uk>
Cc:     netdev@...r.kernel.org
Subject: Re: [drivers/net/phy/sfp] intermittent failure in state machine
 checks

On 09/01/2020 14:41, Andrew Lunn wrote:
> On Thu, Jan 09, 2020 at 01:47:31PM +0000, ѽ҉ᶬḳ℠ wrote:
>> On node with 4.19.93 and a SFP module (specs at the bottom) the following is
>> intermittently observed:
> Please make sure Russell King is in Cc: for SFP issues.
>
> The state machine has been reworked recently. Please could you try
> net-next, or 5.5-rc5.
>
> Thanks
> 	Andrew
Unfortunately testing those branches is not feasible since the router 
(see architecture below) that host the SFP module deploys the OpenWrt 
downstream distro with LTS kernels - in their Master development branch 
4.19.93 being the most recent on offer.

Could the reworked state machine code commits be deployed as patches 
with 4.19 kernel, and if so which commits would that be?
Or, if not will those commits eventually ride the trains to the LTS 
branches and what would be the expected time frame for such uplift?

The problem is with those failing state machine checks is an 
inconvenient disruption in the node's WAN connectivity, often needing to 
reboot the node to get the connectivity reinstated.

Not sure whether pertinent at all (aka being clueless) but noticed that 
for big endian systems a check for an inverted LOS Signal is implemented 
but not for little endian systems.

___
Architecture:        armv7l
Byte Order:          Little Endian
CPU(s):              2
On-line CPU(s) list: 0,1
Thread(s) per core:  1
Core(s) per socket:  2
Socket(s):           1
Vendor ID:           ARM
Model:               1
Model name:          Cortex-A9
Stepping:            r4p1
BogoMIPS:            1600.00
Flags:               half thumb fastmult vfp edsp neon vfpv3 tls vfpd32