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

Fri, Apr 25, 2025 at 10:45:29PM +0200, kuba@...nel.org wrote:
>On Fri, 25 Apr 2025 09:27:19 +0200 Jiri Pirko wrote:
>> info_fuid is the devlink info function.uid I'm introducing.
>> the "fuid" under port is the port function uid attr from the RFC
>> patchset.
>> 
>> Is it clearer now? Should I extend the diagram by something you miss?
>
>Yes, it is clear. The eswitch side makes sense.

Good.

>You just need to find a better place to expose the client side.

Okay. Why exactly you find it wrong to put it under devlink dev info?
I mean, to me it is perfect fit. It is basically another serial number,
uniqueue identification of devlink device.

If other place is better fit, I don't see it. Do you have some ideas?