netdev - Re: [net-next 15/15] net/mlx5: Implement management PF Ethernet profile

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: <ZZyDpJamg9gxDnym@x130>
Date: Mon, 8 Jan 2024 15:22:12 -0800
From: Saeed Mahameed <saeed@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: "Nelson, Shannon" <shannon.nelson@....com>,
	"David S. Miller" <davem@...emloft.net>,
	Paolo Abeni <pabeni@...hat.com>, Eric Dumazet <edumazet@...gle.com>,
	Saeed Mahameed <saeedm@...dia.com>, netdev@...r.kernel.org,
	Tariq Toukan <tariqt@...dia.com>, Armen Ratner <armeng@...dia.com>,
	Daniel Jurgens <danielj@...dia.com>
Subject: Re: [net-next 15/15] net/mlx5: Implement management PF Ethernet
 profile

On 04 Jan 14:44, Jakub Kicinski wrote:
>On Thu, 21 Dec 2023 14:25:33 -0800 Saeed Mahameed wrote:
>> Maybe we should have made it clear here as well, this management PF just
>> exposes a netdev on the embedded ARM that will be used to communicate
>> with the device onboard BMC via NC-SI, so it meant to be used
>> only by standard tools.
>
>How's that different to any other BMC via NC-SI setup?
>NC-SI is supposed to steal packets which were directed to the wire.
>

This is embedded core switchdev setup, there is no PF representor, only
uplink and VF/SF representors, the term management PF is only FW
terminology, since uplink traffic is controlled by the admin, and uplink
interface represents what goes in/out the wire, the current FW architecture
demands that BMC/NCSI traffic goes through a separate PF that is not the
uplink since the uplink rules are managed purely by the eswitch admin.