netdev - Re: [RFC PATCH net-next 0/4] ethtool: Add ability to write to transceiver module EEPROMs

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:   Tue, 29 Jun 2021 21:44:08 +0200
From:   Pali Rohár <pali@...nel.org>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     Ido Schimmel <idosch@...sch.org>, netdev@...r.kernel.org,
        davem@...emloft.net, kuba@...nel.org, jiri@...dia.com,
        vladyslavt@...dia.com, moshe@...dia.com, vadimp@...dia.com,
        mkubecek@...e.cz, mlxsw@...dia.com,
        Ido Schimmel <idosch@...dia.com>
Subject: Re: [RFC PATCH net-next 0/4] ethtool: Add ability to write to
 transceiver module EEPROMs

On Tuesday 29 June 2021 15:47:33 Andrew Lunn wrote:
> > Even with the proposed approach, the kernel sits in the middle between
> > the module and user space. As such, it can maintain an "allow list" that
> > only allows access to modules with a specific memory map (CMIS and
> > SFF-8636 for now) and only to a subset of the pages which are
> > standardized by the specifications.
> 
> Hi Ido
> 
> This seems like a reasonable compromise. But i would go further. Limit
> it to just what is needed for firmware upgrade.
> 
>    Andrew

Hello! If this is just because for CMIS firmware upgrade, what about
rather providing kernel driver for CMIS firmware upgrade?