netdev - RE: [RFC net-next 1/1] ethtool: Add support for set eeprom metadata.

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]

Message-ID: <CO2PR11MB00887A3F4C8ABB71421B1651975B0@CO2PR11MB0088.namprd11.prod.outlook.com>
Date:	Sun, 5 Jun 2016 10:16:20 +0000
From:	Yuval Mintz <Yuval.Mintz@...gic.com>
To:	David Miller <davem@...emloft.net>
CC:	netdev <netdev@...r.kernel.org>,
	Sudarsana Kalluru <Sudarsana.Kalluru@...gic.com>
Subject: RE: [RFC net-next 1/1] ethtool: Add support for set eeprom metadata.

> Currently ethtool implementation does not have a way to pass the metadata for
> eeprom related operations. Some adapters have a complicated non-volatile
> memory implementation that requires additional information – there are drivers
> [bnx2x and bnxt] that use the ‘magic’ field in the {G,S}EEPROM  for that purpose,
> although that’s not its intended usage.
> 
> This patch adds a provision to pass the eeprom metadata for
> %ETHTOOL_SEEPROM/%ETHTOOL_GEEPROM implementations. User provided
> metadata will be cached by the driver and assigns a magic value which the
> application need to use for the subsequent {G,S}EEPROM command.

Hi Dave,

This got no comments at all.
What do you want us to with it next? Should we re-send it as a patch?

Thanks,
Yuval