From: Andrew Lunn <andrew@lunn.ch>
To: Ido Schimmel <idosch@idosch.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
jiri@nvidia.com, vladyslavt@nvidia.com, moshe@nvidia.com,
vadimp@nvidia.com, mkubecek@suse.cz, mlxsw@nvidia.com,
Ido Schimmel <idosch@nvidia.com>
Subject: Re: [RFC PATCH net-next 0/4] ethtool: Add ability to write to transceiver module EEPROMs
Date: Tue, 29 Jun 2021 15:47:33 +0200 [thread overview]
Message-ID: <YNskdT/FMWERmtF5@lunn.ch> (raw)
In-Reply-To: <YNl7YlkYGxqsdyqA@shredder>
> 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
next prev parent reply other threads:[~2021-06-29 13:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 7:59 [RFC PATCH net-next 0/4] ethtool: Add ability to write to transceiver module EEPROMs Ido Schimmel
2021-06-23 7:59 ` [RFC PATCH net-next 1/4] ethtool: Extract module EEPROM attributes before validation Ido Schimmel
2021-06-23 7:59 ` [RFC PATCH net-next 2/4] ethtool: Split module EEPROM attributes validation to a function Ido Schimmel
2021-06-23 7:59 ` [RFC PATCH net-next 3/4] ethtool: Add ability to write to transceiver module EEPROM Ido Schimmel
2021-06-23 7:59 ` [RFC PATCH net-next 4/4] mlxsw: core: Add support for module EEPROM write by page Ido Schimmel
2021-06-23 18:44 ` [RFC PATCH net-next 0/4] ethtool: Add ability to write to transceiver module EEPROMs Andrew Lunn
2021-06-24 19:38 ` Ido Schimmel
2021-06-24 20:27 ` Andrew Lunn
2021-06-27 10:33 ` Ido Schimmel
2021-06-27 15:12 ` Andrew Lunn
2021-06-28 7:33 ` Ido Schimmel
2021-06-29 13:47 ` Andrew Lunn [this message]
2021-06-29 19:44 ` Pali Rohár
2021-06-29 20:12 ` Pali Rohár
2021-06-29 17:27 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YNskdT/FMWERmtF5@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=idosch@idosch.org \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mkubecek@suse.cz \
--cc=mlxsw@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=vadimp@nvidia.com \
--cc=vladyslavt@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.