netdev - Re: [PATCH net-next v3 2/3] devlink: add function unique identifier to devlink dev info

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: <20250417183822.4c72fc8e@kernel.org>
Date: Thu, 17 Apr 2025 18:38:22 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
 pabeni@...hat.com, saeedm@...dia.com, leon@...nel.org, tariqt@...dia.com,
 andrew+netdev@...n.ch, horms@...nel.org, donald.hunter@...il.com,
 parav@...dia.com, kalesh-anakkur.purayil@...adcom.com
Subject: Re: [PATCH net-next v3 2/3] devlink: add function unique identifier
 to devlink dev info

On Wed, 16 Apr 2025 23:41:32 +0200 Jiri Pirko wrote:
> A physical device may consists of several PCI physical functions.
> Each of this PCI function's "serial_number" is same because they are
> part of single board. From this serial number, PCI function cannot be
> uniquely referenced in a system.
> 
> Expanding this in slightly more complex system of multi-host
> "board.serial_number" is not even now unique across two hosts.
> 
> Further expanding this for DPU based board, a DPU board has PCI
> functions on the external host as well as DPU internal host.
> Such DPU side PCI physical functions also have the same "serial_number".
> 
> There is a need to identify each PCI function uniquely in a factory.
> We are presently missing this function unique identifier.
> 
> Hence, introduce a function unique identifier, which is uniquely
> identifies a function across one or multiple hosts, also has unique
> identifier with/without DPU based NICs.

Why do you think this should be a property of the instance?
We have PF ports.