netdev - Re: [net-next v1 0/5] introduce PLDM firmware update library

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: <20200728.170733.50204252309115397.davem@davemloft.net>
Date:   Tue, 28 Jul 2020 17:07:33 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     jacob.e.keller@...el.com
Cc:     netdev@...r.kernel.org, kubakici@...pl, jiri@...nulli.us,
        tom@...bertland.com, jiri@...lanox.com, kuba@...nel.org
Subject: Re: [net-next v1 0/5] introduce PLDM firmware update library

From: Jacob Keller <jacob.e.keller@...el.com>
Date: Thu, 23 Jul 2020 17:21:58 -0700

> This series goal is to enable support for updating the ice hardware flash
> using the devlink flash command.
> 
> The ice firmware update files are distributed using the file format
> described by the "PLDM for Firmware Update" standard:
> 
> https://www.dmtf.org/documents/pmci/pldm-firmware-update-specification-100
> 
> Because this file format is standard, this series introduces a new library
> that handles the generic logic for parsing the PLDM file header. The library
> uses a design that is very similar to the Mellanox mlxfw module. That is, a
> simple ops table is setup and device drivers instantiate an instance of the
> pldmfw library with the device specific operations.
> 
> Doing so allows for each device to implement the low level behavior for how
> to interact with its firmware.
> 
> This series includes the library and an implementation for the ice hardware.
> I've removed all of the parameters, and the proposed changes to support
> overwrite mode. I'll be working on the overwrite mask suggestion from Jakub
> as a follow-up series.
> 
> Because the PLDM file format is a standard and not something that is
> specific to the Intel hardware, I opted to place this update library in
> lib/pldmfw. I should note that while I tried to make the library generic, it
> does not attempt to mimic the complete "Update Agent" as defined in the
> standard. This is mostly due to the fact that the actual interfaces exposed
> to software for the ice hardware would not allow this.
> 
> This series depends on some work just recently and is based on top of the
> patch series sent by Tony published at:
> 
> https://lore.kernel.org/netdev/20200723234720.1547308-1-anthony.l.nguyen@intel.com/T/#t
 ...

Series applied, thanks.