linux-kernel - Re: [RFC PATCH 0/5] Firmware Upload Framework

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: <bd55273c-8eb6-840f-7d1e-0ff98734fe38@redhat.com>
Date:   Thu, 9 Dec 2021 10:55:50 -0800
From:   Tom Rix <trix@...hat.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Bjorn Andersson <bjorn.andersson@...aro.org>,
        Russ Weight <russell.h.weight@...el.com>, sudeep.holla@....com,
        cristian.marussi@....com, ardb@...nel.org,
        linux-kernel@...r.kernel.org, lgoncalv@...hat.com,
        yilun.xu@...el.com, hao.wu@...el.com, matthew.gerlach@...el.com,
        "Gong, Richard" <richard.gong@...el.com>
Subject: Re: [RFC PATCH 0/5] Firmware Upload Framework


On 12/9/21 7:34 AM, Greg KH wrote:
> On Thu, Dec 09, 2021 at 07:15:06AM -0800, Tom Rix wrote:
>> On 11/17/21 11:20 AM, Bjorn Andersson wrote:
>>> On Mon 15 Nov 05:57 PST 2021, Tom Rix wrote:
>>>
>>>> On 11/10/21 5:13 PM, Russ Weight wrote:
>>>>> The Firmware Upload framework provides a common API for uploading firmware
>>>>> files to target devices. An example use case involves FPGA devices that
>>>>> load FPGA, Card BMC, and firmware images from FLASH when the card boots.
>>>>> Users need the ability to update these firmware images while the card is
>>>>> in use.
>>>>>
>>>>> Device drivers that instantiate the Firmware Upload class driver will
>>>>> interact with the target device to transfer and authenticate the firmware
>>>>> data. Uploads are performed in the context of a kernel worker thread in
>>>>> order to facilitate progress indicators during lengthy uploads.
>>>>>
>>>>> This driver was previously submitted in the context of the FPGA sub-
>>>>> system as the "FPGA Image Load Framework", but the framework is generic
>>>>> enough to support other devices as well. The previous submission of this
>>>>> patch-set can be viewed here:
>>>>>
>>>>> https://marc.info/?l=linux-kernel&m=163295640216820&w=2
>>>>>
>>>>> The n3000bmc-sec-update driver is the first driver to use the Firmware
>>>>> Upload API. A recent version of these patches can be viewed here:
>>>>>
>>>>> https://marc.info/?l=linux-kernel&m=163295697217095&w=2
>>>>>
>>>>> I don't think I am duplicating any functionality that is currently covered
>>>>> in the firmware subsystem. I appreciate your feedback on these patches.
>>>> This may be a common api for fpga/dfl-, but it is not likely common for
>>>> general devices.
>>>>
>>> During my years of hacking on device drivers I've run into the need for
>>> being able to reflash/update firmware in things such as touchscreen
>>> controllers, hdmi bridges, usb network devices and (embedded) usb hubs.
>>>
>>> The implementation typically manifest itself as some sysfs or debugfs
>>> knob which when written triggers a request_firmware() followed by the
>>> operation to write the content to flash. But the result is often quite
>>> hacky and requires that you store the firmware-to-be-written in some
>>> path that will be looked at by request_firmware() - and hence these
>>> patches often doesn't end up upstream.
>>>
>>> So I'm certainly in favor of some generic way for drivers to expose an
>>> interface for userspace to flash new firmware to their associated
>>> hardware.
>> The image to be loaded is not really firmware and not really a partial
>> reconfiguration image.  It is both.
> The kernel does not care.  It is a "blob of data to be sent to the
> device".  Traditionally we have called this "firmware", and so the api
> is called that.  But it could be anything, the kernel does not parse it
> or care at all, it is just a pipe from userspace to the device to
> transfer the data.
>
>> Which image is used depends on the end user's workload for the n3000 and
>> could change and need reloading day to day.
>>
>> Because the n3000 is unusable without this change, I would like to see
>> updating working first for the n3000.
>>
>> Then the interface generalized as other devices are found that have a
>> similar use case.
>>
>> This is a device specific feature so it should go somewhere like
>> drivers/fpga/dfl-n3000-update.c
> Then have that driver call the firmware api, that's what it is there
> for.

Yes.

My point is this patchset has had several iterations on inventing a 
general interface that is used only by the n3000 board and possibly some 
of the other dfl boards.  Let's not do another round of a general 
interface inventing.  Let's focus on solving only n3000.

As an example of reducing the scope of the changes,

My understanding of the n3000 is that it does not have hw support for 
partial reconfiguration, there is only this full reimaging using the 
boards bmc, this is the intel-m10-bmc-sec-update change.  A solution 
would be to have a n3000 version of the fpga_manager_ops, with the ops 
using the intel-m10-bmc-sec-update lower level routines and reuse the 
fpga_manager's firmware api high level calls.

Tom


>
> thanks,
>
> greg k-h
>