netdev - Re: [PATCH v4 net-next 00/11] Devlink health reporting and recovery system

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20190207.103712.1253758889021796767.davem@davemloft.net>
Date:   Thu, 07 Feb 2019 10:37:12 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     eranbe@...lanox.com
Cc:     netdev@...r.kernel.org, saeedm@...lanox.com, jiri@...lanox.com,
        moshe@...lanox.com, ayal@...lanox.com
Subject: Re: [PATCH v4 net-next 00/11] Devlink health reporting and
 recovery system

From: Eran Ben Elisha <eranbe@...lanox.com>
Date: Thu,  7 Feb 2019 11:36:31 +0200

> The health mechanism is targeted for Real Time Alerting, in order to know when
> something bad had happened to a PCI device
> - Provide alert debug information
> - Self healing
> - If problem needs vendor support, provide a way to gather all needed debugging
>   information.
> 
> The main idea is to unify and centralize driver health reports in the
> generic devlink instance and allow the user to set different
> attributes of the health reporting and recovery procedures.
 ...

Series applied, thank you.