netdev - Re: [PATCH net-next 0/3] devlink: add the ability to update device flash

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]

Date:   Sun, 17 Feb 2019 15:28:13 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     jakub.kicinski@...ronome.com
Cc:     jiri@...nulli.us, netdev@...r.kernel.org,
        oss-drivers@...ronome.com, mkubecek@...e.cz, andrew@...n.ch
Subject: Re: [PATCH net-next 0/3] devlink: add the ability to update device
 flash

From: Jakub Kicinski <jakub.kicinski@...ronome.com>
Date: Thu, 14 Feb 2019 13:40:43 -0800

> This series is the second step to allow trouble shooting and recovering
> devices in bad state without the use of netdevs as handles.  We can
> already query FW versions over devlink, now we add the ability to update
> the FW.  This will allow drivers to implement some from of "limp-mode"
> where the device can't really be used for networking and hence has no
> netdev, but we can interrogate it over devlink and fix the broken FW.
> 
> Small but nice advantage of devlink is that it only holds the devlink
> instance lock during flashing, unlike ethtool which holds rtnl_lock().

Series applied, thanks Jakub.

Looking at the feedback, the things requested can be done as follow-ups
quite easily.