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  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:   Thu, 14 May 2020 12:06:59 -0700
From:   Jakub Kicinski <>
To:     Igor Russkikh <>
Cc:     <>, "David S . Miller" <>,
        Ariel Elior <>,
        Michal Kalderon <>,
        Denis Bolotin <>
Subject: Re: [PATCH v2 net-next 00/11] net: qed/qede: critical hw error

On Thu, 14 May 2020 12:57:16 +0300 Igor Russkikh wrote:
> FastLinQ devices as a complex systems may observe various hardware
> level error conditions, both severe and recoverable.
> Driver is able to detect and report this, but so far it only did
> trace/dmesg based reporting.
> Here we implement an extended hw error detection, service task
> handler captures a dump for the later analysis.
> I also resubmit a patch from Denis Bolotin on tx timeout handler,
> addressing David's comment regarding recovery procedure as an extra
> reaction on this event.
> v2:
> Removing the patch with ethtool dump and udev magic. Its quite isolated,
> I'm working on devlink based logic for this separately.
> v1:

I'm not 100% happy that the debug data gets reported to the management
FW before the devlink health code is in place. For the Linux community,
I think, having standard Linux interfaces implemented first is the

Powered by blists - more mailing lists