netdev - Re: [PATCH net-next v2 0/3] mlxsw: Add 'fw_load

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] [day] [month] [year] [list]

Message-Id: <20181203.135605.354486063267163970.davem@davemloft.net>
Date:   Mon, 03 Dec 2018 13:56:05 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     idosch@...lanox.com
Cc:     netdev@...r.kernel.org, jiri@...lanox.com, shalomt@...lanox.com,
        jakub.kicinski@...ronome.com, andrew@...n.ch, f.fainelli@...il.com,
        dsahern@...il.com, andy@...yhouse.net, alexpe@...lanox.com,
        mlxsw@...lanox.com
Subject: Re: [PATCH net-next v2 0/3] mlxsw: Add 'fw_load_policy' devlink
 parameter

From: Ido Schimmel <idosch@...lanox.com>
Date: Mon, 3 Dec 2018 07:58:57 +0000

> Shalom says:
> 
> Currently, drivers do not have the ability to control the firmware
> loading policy and they always use their own fixed policy. This prevents
> drivers from running the device with a different firmware version for
> testing and/or debugging purposes. For example, testing a firmware bug
> fix.
> 
> For these situations, the new devlink generic parameter,
> 'fw_load_policy', gives the ability to control this option and allows
> drivers to run with a different firmware version than required by the
> driver.
> 
> Patch #1 adds the new parameter to devlink. The other two patches, #2
> and #3, add support for this parameter in the mlxsw driver.
> 
> Example:
 ...
> iproute2 patches available here:
> https://github.com/tshalom/iproute2-next
> 
> v2:
> * Change 'fw_version_check' to 'fw_load_policy' with values 'driver' and
>   'flash' (Jakub)

Series applied.