netdev - Re: [patch iproute2-next v4 0/2] devlink: couple forgotten flash patches

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: <7d3ad854-deba-45e2-fb10-b5a9c9587a04@gmail.com>
Date:   Mon, 16 Sep 2019 08:49:11 -0600
From:   David Ahern <dsahern@...il.com>
To:     Jiri Pirko <jiri@...nulli.us>
Cc:     netdev@...r.kernel.org, stephen@...workplumber.org,
        jakub.kicinski@...ronome.com, saeedm@...lanox.com,
        mlxsw@...lanox.com, f.fainelli@...il.com
Subject: Re: [patch iproute2-next v4 0/2] devlink: couple forgotten flash
 patches

On 9/16/19 4:09 AM, Jiri Pirko wrote:
> The fact that the file is expected to be in /lib/firmware is in the
> devlink flash description right above:
> 
> 
>    devlink dev flash - write device's non-volatile memory.
>        DEV - specifies the devlink device to write to.
> 
>        file PATH - Path to the file which will be written into device's flash. The path needs to be relative to one of the directories
>        searched by the kernel firmware loaded, such as /lib/firmware. 

fine. applied both to iproute2-next.